agentleFS
muslewskimuslewski/status-herald/.claude/skills/atlas-update/SKILL.md

atlas-update

Skill2 starsChanged 4 months agoMITView on GitHub

Use when the user wants to update atlas, an atlas update is available, doctor or status reports a version nudge / pending migrations, or they ask to bring the vault to latest. Deterministic migrate first; this skill handles AI-merge of locally edited vendored files.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. muslewski/token-oracle★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. razvan-sc/claude-atlas★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ground truth first: Run both dry commands and act only on their output — never on memory of what atlas does:

    line 18
  2. Distinctive:

    Read the local file on disk.

    line 29
  3. Very specific:

    Read the upstream version from the installed package (node_modules/memory-atlas/skills/… for skills, or the block text atlas wire would …

    line 30
  4. Very specific:

    Never modify zone cards, decisions, specs, plans, reports, or atlas.config.json values the user set.

    line 53
  5. Distinctive:

    Stop and ask on any ambiguity.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Atlas update — bring an adopting repo to the installed toolkit version

The toolkit owns deterministic transforms (atlas migrate). You own the judgment layer: merging locally edited on-ramp blocks and vendored skills without destroying user customizations.

Procedure

  1. Ground truth first. Run both dry commands and act only on their output — never on memory of what atlas does:
    • npx --no-install atlas doctor
    • npx --no-install atlas migrate (dry-run; no --write)
  2. Apply deterministic migrations. Echo the migrate plan to the user, then run:
    • npx --no-install atlas migrate --write
  3. Reconcile every ⚠ locally edited vendored item. For each one doctor lists:
    • Read the local file on disk.
    • Read the upstream version from the installed package (node_modules/memory-atlas/skills/… for skills, or the block text atlas wire would render for on-ramp markers).
    • Merge by judgment: preserve every local customization; adopt upstream structure and additions. When local and upstream conflict on the same line, keep local and note it in the summary. Never resolve by deleting user content.
  4. Re-wire. npx --no-install atlas wire all — pristine blocks/hooks re-render; your merged files keep their new hashes recorded in .atlas-state.json.
  5. Verify.
    • npx --no-install atlas check
    • npx --no-install atlas doctor
    • Doctor must end all-✓ except deliberate locally edited items you just reconciled (and any pre-existing intentional local edits you left).
  6. Report. One diff summary: files touched, migrations applied, conflicts kept-local.

HARD RULES

  • Never modify zone cards, decisions, specs, plans, reports, or atlas.config.json values the user set.
  • Migrations and wire may only touch machine-owned artifacts (state file, content inside atlas markers, vendored skill copies, hook wiring).
  • Stop and ask on any ambiguity.
  • Dry-run before every write path (atlas migrate without --write first; never invent filesystem writes the CLI does not perform).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.