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

wiki-status

Skill0 starsChanged 4 months agoMITView on GitHub

Diagnose vault readiness, integrations, and configured capabilities. Use for status, health checks, or pre-research verification.

4 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:

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

    line 12
  2. Very specific:

    Run llm-wiki doctor for the deterministic vault diagnostic.

    line 16
  3. Very specific:

    Run llm-wiki integrations status when integrations matter to the user’s task.

    line 17
  4. Distinctive:

    Read the dashboard checks only for a full environment report, index/KG diagnosis, or explicit troubleshooting.

    line 23

“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 status — health dashboard

Vault path preamble

Never inspect a bare Path("llm-wiki/"). Start with llm-wiki doctor, which resolves and validates the vault. If direct filesystem inspection is necessary, resolve LLM_WIKI_VAULT first and use that root consistently.

Workflow

  1. Run llm-wiki doctor for the deterministic vault diagnostic.
  2. Run llm-wiki integrations status when integrations matter to the user’s task.
  3. Report readiness and the smallest safe remediation for anything missing or degraded.
  4. Offer wiki-setup for a missing or incomplete vault; do not change configuration during a status check.

Progressive disclosure

Read the dashboard checks only for a full environment report, index/KG diagnosis, or explicit troubleshooting.

Done looks like

  • The user knows whether the resolved vault is ready.
  • Issues identify their affected capability and an actionable next command.
  • Secrets remain masked and no configuration changes are made.

Related skills

  • wiki-setup — initialize or complete the vault.
  • wiki-onboard — route a new user to the right first action.

Smoke check

  • CLI: llm-wiki doctor (and llm-wiki integrations status when integrations matter).
  • Prompt: Invoke this skill; confirm it reports readiness without changing config.json.

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