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

wiki-maintainer

Skill0 starsChanged 4 months agoMITView on GitHub

Maintains the LLM Wiki vault — index, log, cross-links, contradictions. Use when editing llm-wiki/wiki/, merging ingested sources, or keeping the wiki consistent.

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

8 rules. About 0 are common, 1 is distinctive, and 7 are 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.

  • 7

    Very specific

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

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

    Read llm-wiki/CLAUDE.md and wiki/index.md first.

    line 13
  2. Very specific:

    If git.enabled and git.include_diff_in_skill_context, run llm-wiki git diff (vault root) for context (truncate if huge).

    line 14
  3. Very specific:

    Ensure wiki/index.md lists new or renamed topics (one-line entries when appropriate).

    line 20
  4. Distinctive:

    Remove or update stale index lines when pages are deleted or moved.

    line 21
  5. Very specific:

    Add or fix [[wikilinks]] where it helps navigation.

    line 25
  6. Very specific:

    If two pages contradict, surface the conflict in wiki/log.md or a dedicated note — do not silently pick a winner without evidence.

    line 26
  7. Very specific:

    If viewer.enabled is not false in config:

    line 34
  8. Very specific:

    If vault git is used, user knows whether to run llm-wiki git snapshot (per project convention).

    line 47

≈ “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 maintainer — Curator

You own the curated layer under llm-wiki/wiki/. Sources live in llm-wiki/raw/ (immutable except via llm-wiki ingest). After substantive edits or merges, keep wiki/index.md, wiki/log.md, and [[wikilinks]] coherent.

Pre-flight

  1. Read llm-wiki/CLAUDE.md and wiki/index.md first.
  2. If git.enabled and git.include_diff_in_skill_context, run llm-wiki git diff (vault root) for context (truncate if huge).

Steps

Step 1 — Reconcile index and pages

  • Ensure wiki/index.md lists new or renamed topics (one-line entries when appropriate).
  • Remove or update stale index lines when pages are deleted or moved.

Step 2 — Cross-links and structure

  • Add or fix [[wikilinks]] where it helps navigation; avoid orphan targets (create stubs or remove links).
  • If two pages contradict, surface the conflict in wiki/log.md or a dedicated note — do not silently pick a winner without evidence.

Step 3 — Log

  • Append wiki/log.md with date, scope, and files touched for non-trivial maintenance passes.

Step 4 — Refresh site viewer

If viewer.enabled is not false in config:

llm-wiki build-site --if-stale

This rebuilds wiki/.og/ only when wiki content is newer than the last build.

Done looks like

  • wiki/index.md reflects actual wiki/**/*.md pages (no stale-only index lines for missing pages unless intentional stubs).
  • Broken [[wikilinks]] to missing targets are fixed or flagged.
  • wiki/log.md records meaningful maintenance when appropriate.
  • If vault git is used, user knows whether to run llm-wiki git snapshot (per project convention).

Artifacts

ReadsWrites
llm-wiki/CLAUDE.md, wiki/index.md, wiki/**/*.mdwiki/index.md, wiki/log.md, wiki/**/*.md

Downstream: wiki-lint, wiki-pipeline (validate stage). See skills/references/pipeline-artifacts.md.

Related skills

  • wiki-ingest — merge new raw/ material into topic pages (often precedes maintainer pass).
  • wiki-lint — orphans, contradictions, gaps.
  • wiki-raw-prepare — clean messy raw/ before merge when needed.
  • wiki-query — read-only Q&A from wiki.
  • wiki-session-memory — per-chat notes in raw/memory/

See references/workflows.md for ingest/query/lint outlines.

Smoke check

  • CLI: From the vault root: llm-wiki validate and, if vault git is enabled, llm-wiki git status.
  • Prompt: Invoke this skill by name; confirm Pre-flight reads llm-wiki/CLAUDE.md and wiki/index.md.

Optional: skills/references/context-persona.md and persona.name in llm-wiki/config.json (default Gennie).

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