agentleFS
Sign inStart free
nathanadaynathanaday/claude-atlas/skills/wiki-save/SKILL.md

wiki-save

Skill1 starsChanged 37 days agoMITView on GitHub

Keep something from this conversation in the wiki: an answer, a decision, a comparison, a finding, cited to this session. Use for save this, keep this answer, file this decision, remember this in the wiki. Files are wiki-ingest; an idea to act on later is a note in scratchpad/ (the almagest skill).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Write the passage to keep, in full: the answer, the decision and its reasons, and the documents the conversation relied on, as links.

    line 19
  2. Very specific:

    Call source with action: capture, text, a title, tags (the tags that exist and fit its subject.

    line 21

≈ “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.

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

wiki-save

A saved passage enters the wiki the way every other document does: as a source that a change absorbs. The source is the passage itself, so the topics cite a document that holds the claims, and its locator names this session.

Tools: source capture. Skills: wiki-sync. References: changes.md, pages.md.

Procedure

  1. Name exactly what to keep. When the user's "this" could mean two things, quote both and ask.
  2. Write the passage to keep, in full: the answer, the decision and its reasons, and the documents the conversation relied on, as links.
  3. Call source with action: capture, text, a title, tags (the tags that exist and fit its subject; name a new one to the user, and set new_tags: true in tagging: known mode only after the user agreed), and locator set to this session's document as a link (the session-start context names it: [[2026-09-27 1432 a1b2c3]]). The source gets origin: pasted.
  4. Hand the new source to wiki-sync. In its change, the modify of the source sets authority: synthetic.

Gate

The gate of wiki-sync.

Hand off

None.

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.

Check your setup, free