agentleFS
Sign inStart free
nathanadaynathanaday/almagest/skills/almagest-onboard/SKILL.md

almagest-onboard

Skill1 starsChanged 25 days agoMITView on GitHub

Make a new Almagest vault: ask its name, its folder, and how freely to tag, then link its first repositories. Use for set up almagest, new vault, start a vault here, onboard, make this folder a vault. Linking a repository to a vault that exists is repo-link.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Ask for the vault's name and folder in one question.

    line 17
  2. Distinctive:

    Ask the tag question, with option 1 as the default:

    line 21
  3. Very specific:

    Ask for one or two sentences on what the vault is for.

    line 26
  4. Very specific:

    Call vault with action: init, name, path, tagging (open or known), and description.

    line 28

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

almagest-onboard

A vault is one Obsidian vault and one git repository that holds every document of the user's work: the sources, repositories, and topics of the wiki, the sessions, and the changes. This skill asks the three questions a vault needs, makes it, and offers to link the first repositories.

Tools: vault init. Skills: repo-link.

Procedure

  1. Ask for the vault's name and folder in one question. The default folder is the working directory when it is empty. A folder that already holds notes, or that is already the root of a git repository, is adopted as it is. A folder inside another repository is refused: the vault must be the root of its own history.
  2. Ask the tag question, with option 1 as the default:
    1. "Tag freely; I will tidy later" (open): the agent adds a tag when no tag that exists fits, and names each new tag in the preview;
    2. "Use my tags; ask before a new one" (known): the agent uses only tags that some document holds, and asks before it adds one.
  3. Ask for one or two sentences on what the vault is for. They become the body of Almagest.md, the context every session reads first.
  4. Call vault with action: init, name, path, tagging (open or known), and description.
  5. Offer to link repositories. The user names paths, or a folder that holds repositories: then list the git work trees one level below it (ls and a check for .git) and let the user pick. Hand the list to repo-link, which links them in one change and proposes the tags of each.
  6. Tell the user to open the vault in Obsidian (almagest open --register, or Open folder as vault) and, for its interface, to install Almagest from Obsidian's community plugins (obsidian://show-plugin?id=almagest). The vault works without the plugin. The plugin adds the colors and icons of the callouts, the Approve and Cancel buttons in each change document, the Almagest palette (Ingest, Wiki lint, Journals, Checkouts, the agent sessions, and Safe delete), the repository panel, and quiet snapshots of the user's edits. Recommend Duet too (obsidian://show-plugin?id=duet), and say it is optional: with Duet, the agents that the palette starts work in a note of the vault; without it, they start in a new terminal. The setting "Agent conversations" chooses.

Gate

vault init writes only after steps 1 to 3 are answered. repo-link has its own gate.

Hand off

repo-link, then repo-ingest for each repository the user wants described now; wiki-ingest when the user has files to add.

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