agentleFS
SkinnnyJaySkinnnyJay/wiki-llm/skills/wiki-setup/SKILL.md

wiki-setup

Skill0 starsChanged 4 months agoMITView on GitHub

Interactive vault setup wizard that previews configuration before scaffolding. Use for setup, initialization, or guided configuration.

5 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

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Iron rule: Never write config.json, scaffold files, set environment variables, or initialize Git until the user explicitly confirms the …

    line 10
  2. Very specific:

    Never use a bare Path("llm-wiki/").

    line 14
  3. Distinctive:

    Ask only the configuration questions needed for that route.

    line 20
  4. Very specific:

    Use the setup wizard runbook for question groups, backend choices, and apply details.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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 setup — interactive wizard

Iron rule: Never write config.json, scaffold files, set environment variables, or initialize Git until the user explicitly confirms the final preview.

Vault path preamble

Never use a bare Path("llm-wiki/"). Prefer llm-wiki CLI commands so the vault is resolved consistently. For direct filesystem work, resolve LLM_WIKI_VAULT; if it is unavailable, run llm-wiki doctor and ask the user to select or initialize the vault.

Workflow

  1. Determine whether the user wants a full setup, vault-only setup, or memory-only setup.
  2. Confirm the current state with llm-wiki doctor; memory-only requires an existing vault.
  3. Ask only the configuration questions needed for that route.
  4. Show the complete effective configuration and proposed filesystem changes.
  5. Apply only after confirmation, then suggest llm-wiki doctor and llm-wiki integrations status.

Progressive disclosure

Use the setup wizard runbook for question groups, backend choices, and apply details. Use docs/QUICKSTART.md for the unattended defaults path.

Done looks like

  • The user approved a preview and the selected vault is initialized with the intended configuration.
  • A cancellation leaves configuration and filesystem state unchanged.

Related skills

  • wiki-status — verify readiness after setup.
  • wiki-onboard — route a first-time user to setup, configuration, or diagnosis.

Smoke check

  • CLI: llm-wiki setup --help (and llm-wiki doctor after a confirmed setup).
  • Prompt: Invoke this skill; confirm it shows a full config preview and waits for explicit confirmation before writing.

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.