node-drift
Skill4 starsChanged 4 months agoMITView on GitHub
Use when the user asks whether Officina node certificates are current or stale, or asks for canonical node hashes. Do not use to issue certificates.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bib-auditSkill
- bootstrap-dispatcher-runtimeSkill
- ci-debugSkill
- cloud-filesSkill
- connect-googleSkill
- daily-planSkill
- distill-to-ruttersSkill
- email-clientSkill
- email-triageSkill
- find-handoff-candidatesSkill
- formal-prose-reviewSkill
- get-weatherSkill
- git-workflowSkill
- hook-makerSkill
- initialize-tddSkill
- install-launchersSkill
- latex-workshopSkill
- list-managerSkill
- llm-wakeupSkill
- loose-modeSkill
- make-tex-docstringSkill
- math-dependency-graphSkill
- milestone-loggingSkill
- node-certifySkill
- notation-reviewSkill
- online-calendarSkill
- pdf-to-markdownSkill
- prepare-handoffSkill
- proof-auditSkill
- recurring-tasksSkill
- refactor-nodeSkill
- regenerate-blueprintsSkill
- relocate-nodesSkill
- semantic-integrationSkill
- send-feedbackSkill
- setup-interface-managerSkill
- skill-makerSkill
- technical-flow-reviewSkill
- tight-modeSkill
- tool-applicabilitySkill
- update-standardsSkill
- using-compassSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Use node-drift._rtx.interface.drift-status to read signed certificate currentness and node-drift._rtx.interface.compute-hashes to read the …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- BEGIN BLUEPRINT INTERFACES -->Generated from
blueprint.yaml. Do not edit this block by hand.
Executable Interfaces:
Send the required caller (caller skill), interface, version, and arguments; optional dry_run defaults to false. Compact uses ordered positionals plus an option mapping; ordered raw argv uses positionals: [] plus every argv token in list options. Never mix forms.
node-drift._rtx.interface.compute-hashes— Compute canonical certification-basis and v6 node hashes for exact or installed modules.- Caller:
node-drift - Version: 2
- Security level: 2
- Alternative:
defaultArguments JSON (replace labels with actual values). Omit optional positionals and options that are not needed. {"options": {"--json": true, "--repo-root": "ROOT", "--skill-root": "ROOT"}, "positionals": ["target..."], "stdin": null} Required options: []; positional arity: 0..unbounded; stdin: forbidden
- Caller:
node-drift._rtx.interface.drift-status— Read signed certificate currentness, exact structured drift causes, and the dependency-first stale worklist for exact or installed v6 modules without writing certification state.- Caller:
node-drift - Version: 4
- Security level: 2
- Alternative:
defaultArguments JSON (replace labels with actual values). Omit optional positionals and options that are not needed. {"options": {"--all": true, "--dag-file": "PATH", "--json": true, "--repo-root": "ROOT", "--skill-root": "ROOT"}, "positionals": ["target..."], "stdin": null} Required options: []; positional arity: 0..unbounded; stdin: forbidden
- Caller:
<!-- END BLUEPRINT INTERFACES -->Use node-drift._rtx.interface.drift-status to read signed certificate
currentness and node-drift._rtx.interface.compute-hashes to read the canonical
certification-basis and node hashes.
Both routes accept only canonical version-6 repository graphs. They derive state through the shared certification view and never create keys, sign payloads, append certificates, run validators, or execute target code.
An exact --repo-root request selects the repository's complete canonical module
graph. The route supplies its own status or compute-hashes subcommand; callers
must not pass it.
An exact --skill-root request selects the dependency closure rooted at that
module's owned nodes. Named requests resolve matching installed copies across
supported hosts. With no target, the checker scans observed installed module
roots.
JSON status is certification-state read-only. Human-readable status also saves
a derived report under _build/certificate-drift-<timestamp>.md; that report
has no certification authority. Hash output never writes a report.
For one exact repository, JSON status may receive --dag-file PATH. It writes
the complete neutral dependency DAG as
officina.certification-dependency-dag/v1 and adds dag_file plus the sorted
stale_vertices projection to stdout. The DAG and projection describe drift;
they contain no audit state and do not authorize certification.
Report certificate-current only when every selected node has a valid signed
certificate matching its current node hash, dependencies, certification basis,
certifier functional identity, and expected checks. The signed source_commit
is issuance provenance for restoring the issued snapshot; it is not required
to equal current HEAD. Otherwise report certificate-stale with a stale
worklist that maps exact changed file, interface, or dependency causes to the
affected facets and nodes. Manifest mismatches name added, removed, or changed
files. Dependency deltas cover all direct facet dependencies: they use the
interface id when present, or relation and target otherwise. Broad certificate,
basis, or graph concerns remain node-scoped rather than being misreported as a
narrow facet change.
Writing certification state belongs solely to node-certify.
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.

