agentleFS
Sign inStart free
SkinnnyJaySkinnnyJay/wiki-llm/skills/wiki-onboard/SKILL.md

wiki-onboard

Skill0 starsChanged 4 months agoMITView on GitHub

First-run router for a new or existing llm-wiki vault.

The file

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:

    Use this brief conversational router before a first workflow.

    line 10
  2. Very specific:

    Never assume the vault is Path("llm-wiki/").

    line 14
  3. Distinctive:

    Ask the questions in references/questions.md, one at a time as needed.

    line 16
  4. Very specific:

    After setup or configuration, recommend llm-wiki doctor to confirm readiness.

    line 20

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

Use this brief conversational router before a first workflow. Do not edit files until the destination flow asks for confirmation.

Vault path preamble

Never assume the vault is Path("llm-wiki/"). Use llm-wiki doctor to locate and diagnose the vault; for direct filesystem work, resolve LLM_WIKI_VAULT first and use the resolved root consistently.

  1. Ask the questions in references/questions.md, one at a time as needed.
  2. Route a missing vault or missing config.json to /llm-wiki:setup.
  3. Route a healthy existing vault with desired setting changes to /llm-wiki:configure.
  4. Route an existing vault with errors, uncertain setup, or a failed check to llm-wiki doctor. Explain that --fix creates only missing vault directories and restores safe blank defaults; it never deletes vault content or replaces secrets.
  5. After setup or configuration, recommend llm-wiki doctor to confirm readiness.

Quick terminal check

llm-wiki doctor

Smoke check

  • CLI: llm-wiki doctor from a project with a vault (LLM_WIKI_VAULT or ./llm-wiki).
  • Prompt: Invoke this skill for a first-time user; confirm it asks routing questions and does not write files before the destination flow.

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