preference-update
Skill142 starsChanged 3 months agoApache-2.0View on GitHub
Update a bounded preference policy from the user's repeated corrections, without ever overwriting the user's own choices.
In this repository62 other files it gives its agents.
- examples/recipes/partners/hpe/retail-assistant/docker-compose/scripts/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/hpe/retail-assistant/helm/files/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/tavily/watchtower/prompts/AGENTS.mdAGENTS.md
- nemoclaw-community-contributor-examplesSkill
- nemoclaw-community-maintainer-policiesSkill
- coach-nemoclaw-hermesSkill
- coordinate-nemoclaw-blenderSkill
- blender-host-sandbox-boundarySkill
- blender-python-api-verificationSkill
- ovphysx-host-runtime-boundarySkill
- axe-a11ySkill
- deep-researchSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- module-1Skill
- module-2Skill
- module-3Skill
- module-4Skill
- module-5Skill
- module-6Skill
- module-7Skill
- setup-workshop-nemoclaw-operatorSkill
- setup-workshop-nemoclawSkill
- workshopSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- gitlab-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- public-web-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- kubernetes-sreSkill
- openshift-llm-deploySkill
- inbound-judgingSkill
- memory-consolidationSkill
- memory-repairSkill
- memory-writingSkill
- obligation-reviewSkill
- nv-tech-assistantSkill
- payment-ops-playbookSkill
- payment-screeningSkill
- rail-boundary-testSkill
- release-packetSkill
- pr-reviewSkill
- pr-test-case-assistantSkill
- vss-videoSkill
- nemoclaw-hermes-swarmSkill
- blackwall-payment-gateSkill
- retail-apiSkill
- retail-apiSkill
- watchtowerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
All reads of workspace/memory use python3 $HERMES_HOME/scripts/memory_operations.py read <relative-path> ....
- Distinctive: line 18
If it reports a pending or blocked operation, stop this pass and surface the diagnostic.
- Very specific: line 21
All memory file changes, including shared index entries and the single log entry, go through python3 $HERMES_HOME/scripts/apply_memory.py < …
- Very specific: line 23
Never write, append, rename, or delete memory files with shell or file tools.
- Very specific: line 26
Use null text for a reviewed people merge source deletion and include its index removal in the same operation.
- Very specific: line 36
Before building a proposal, read $HERMES_HOME/scripts/memory-protocol.md for the installed JSON contract and examples.
- Distinctive: line 48
Every time the user ignores a row or overrides its priority, they are correcting a judgment.
- Distinctive: line 71
Read the audit trail for user-authored corrections since the last run:
- Very specific: line 111
Read $HERMES_HOME/workspace/policy/preferences.md, creating it with an empty ## Observed Preferences section if absent.
- Distinctive: line 114
If an existing entry already says the same thing — the same pattern in other words counts — do nothing.
- Distinctive: line 133
Read the file back after editing and confirm both that the entry landed and that the cap held.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Coordinated memory transport
All reads of workspace/memory use
python3 $HERMES_HOME/scripts/memory_operations.py read <relative-path> ....
This returns the store instance, exact file hashes, and a coherent snapshot.
If it reports a pending or blocked operation, stop this pass and surface the
diagnostic. Do not read partial files as current memory.
All memory file changes, including shared index entries and the single log
entry, go through python3 $HERMES_HOME/scripts/apply_memory.py < proposal.json.
Never write, append, rename, or delete memory files with shell or file tools.
Prepare complete people/attention pages and their evidence markers together
in a legacy_write proposal with the returned expected_hash for every file.
Use null text for a reviewed people merge source deletion and include its
index removal in the same operation. Preserve the content and admission rules
below. A failed proposal acknowledges no new evidence batch.
Managed projects, patterns, and concepts use update with declared field
changes; never send a managed page through the whole-file adapter. Existing
unmanaged pages may be repaired with their exact full-file precondition and
remain unmanaged. Use repair_index for verified missing or stale entries,
and log_only for a pass that changes only the shared memory log. The writer
constructs index patches and a log entry containing its operation ID.
Before building a proposal, read $HERMES_HOME/scripts/memory-protocol.md
for the installed JSON contract and examples.
A conflict preserves the live file. Report it and defer that target. Generate
a fresh independent proposal for unrelated work; do not retry a changed
request under an already used request ID, adopt a page implicitly, clear
review flags, or use a direct write as a fallback. Per-page user approval is
not required for generated content after Foundation enablement. Handwritten
content requires an explicit scoped user action through correct.py.
Updating preferences from corrections
Every time the user ignores a row or overrides its priority, they are correcting a judgment. One correction is an accident. Three of the same shape is a preference, and a preference belongs in writing where the next run can read it.
Nothing here trains a model. The output is a bounded text policy that later runs read as input — it can be inspected, edited by hand, and deleted, and deleting it returns the system to its default judgment.
This skill reads the audit trail and edits one file. It never touches an obligation.
The invariant
Never write to obligations. Not priority, not manual_priority, not
status. The user's overrides are theirs; this skill only reads them.
A run that changes a row has failed, however good its reasoning was.
The policy lands in $HERMES_HOME/workspace/policy/preferences.md, which
inbound-judging reads as a prior and obligation-review reads as context.
Step 1 — collect
Read the audit trail for user-authored corrections since the last run:
SELECT e.event_type, e.after_json, o.title, o.kind, i.source, i.sender
FROM events e
JOIN obligations o ON o.id = e.obligation_id
JOIN items i ON i.source_id = o.source_id
WHERE e.actor = 'user'
AND e.event_type IN ('ignored', 'priority_override')
AND e.ts > :last_runNote that actor matters. Rows this agent changed are not corrections;
reading your own output back as evidence is how a system talks itself into a
belief.
Step 2 — group
Group the corrections by what they have in common. Useful groupings, roughly in order of how often they turn out to be real:
- the same sender, or the same sender domain,
- the same recurring subject shape — a build notification, a newsletter, an automated digest,
- the same
kindfrom the same source.
A pattern is one plain sentence that would describe most rows in its group. If you cannot write that sentence without listing exceptions, it is not a pattern.
Step 3 — apply the threshold
A pattern qualifies only when it covers at least three corrections. Below that, leave it alone and let the next run decide — two of anything is a coincidence you would be encoding forever.
The threshold is deliberately fixed. A system permitted to lower its own bar for what counts as a preference eventually accepts everything.
Step 4 — write
Read $HERMES_HOME/workspace/policy/preferences.md, creating it with an empty
## Observed Preferences section if absent.
If an existing entry already says the same thing — the same pattern in other words counts — do nothing. Restating a known pattern inflates the file and teaches the reader nothing.
Otherwise append under ## Observed Preferences, newest first:
- [2026-08-18] Automated build notifications from ci@example.com — the user
ignores these; do not create a row unless a human is named in the body.Each entry states the pattern and what to do about it. "Deprioritize newsletters" is not actionable; "newsletters from the vendor list are review-only unless they name a deadline" is.
Cap the section at 20 entries. Past that, drop the oldest. A policy file longer than one screen stops being read, and an unread policy is worse than none — it implies the system is adapting when it is not.
Read the file back after editing and confirm both that the entry landed and that the cap held.
Step 5 — log
Append one entry to $HERMES_HOME/workspace/memory/log.md, including runs that changed
nothing:
## [2026-08-18T09:20:00Z] preference-update
- 7 user corrections since last run, 2 patterns above threshold, 1 already known
- appended: automated build notifications from ci@example.comA run that changed nothing is a useful signal — it means the judging skill is currently matching the user's taste.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

