atlas-adopt
Skill2 starsChanged 4 months agoMITView on GitHub
Use when the user wants to adopt this knowledge base, onboard a brownfield vault, act on "atlas adopt reported unclassified notes", or migrate existing docs/mind into atlas. Deterministic adopt first; this skill classifies leftover notes and proposes zone cards without stamping.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- muslewski/status-heraldword for word, first seen Jul 28, 2026
Other versions1 project uses a version of this.
Word for word · 1
- muslewski/status-herald★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- atlas-navSkill
- atlas-recollectionSkill
- atlas-seedSkill
- atlas-updateSkill
- writing-for-retrievalSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Distinctive: line 19
Ground truth first: Run the dry command and act only on its output — never on memory of the vault:
- Distinctive: line 33
When unsure, list it for the owner instead of guessing.
- Distinctive: line 35
Zone extraction: When an architecture doc describes a coherent subsystem:
- Distinctive: line 54
Never delete user notes.
- Very specific: line 55
Never pre-stamp (verifiedAt stays unverified until a human reviews and runs atlas stamp <slug>).
- Distinctive: line 57
Never edit note bodies during classification — frontmatter + location only.
- Distinctive: line 58
Stop and ask on any ambiguity.
≈ “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.
Files
Atlas adopt — brownfield classification layer
The toolkit owns deterministic transforms (atlas adopt: wikilink zones → bare
slugs, zone honesty, debt type, human-drafts/ → drafts, seed config). You own
the judgment layer: classify unclassified notes, place them in the right
folder, and propose zone cards — never pre-stamp.
Procedure
- Ground truth first. Run the dry command and act only on its output —
never on memory of the vault:
npx --no-install atlas adopt(no--write)
- Apply deterministic transforms when pending. Echo the adopt plan to the
user, then run:
npx --no-install atlas adopt --write
- Classify each
unclassifiednote. For every? <path>line in the report (or still present after--write):- Read the note.
- Classify into Map (zone / flow), Ledger (decision / spec / plan / debt / idea / report), Vision, or out-of-scope.
- Move it into the configured folder and set
type:frontmatter to match. - When unsure, list it for the owner instead of guessing.
- Zone extraction. When an architecture doc describes a coherent
subsystem:
- Propose a zone card from
templates/notes/zone.md(or the vault's copy). - Draft
owns.globsfrom paths the doc names — owner verifies before stamp. - Card starts
status: seeded,verifiedAt: unverified. - NEVER stamp during adoption.
- Propose a zone card from
- Finish wiring and migrations.
npx --no-install atlas wire allnpx --no-install atlas migrate --writenpx --no-install atlas buildnpx --no-install atlas check- Echo remaining warnings to the user.
- Report. One summary: moved / classified / proposed-zones / left-for-owner.
HARD RULES
- Never delete user notes.
- Never pre-stamp (
verifiedAtstaysunverifieduntil a human reviews and runsatlas stamp <slug>). - Never edit note bodies during classification — frontmatter + location only.
- Stop and ask on any ambiguity.
- Dry-run before every write path (
atlas adoptwithout--writefirst).
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.

