agentleFS
ghvinashvilighvinashvili/specagent/.claude/skills/wiki-ingest/SKILL.md

wiki-ingest

Skill7 starsChanged 16 days agoApache-2.0View on GitHub

Compile changed context/ material into wiki pages, update index and log, run the lint. Use when a librarian ingests into wiki/.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-status, wiki-capture and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nexuschainsSkill

    wiki-status

    Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.

    Also in 5 projects that use this

  • jehrhardtSkill

    wiki-capture

    Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.

    Also in 6 projects that use this

  • Ivy-Chen1999Skill

    wiki-research

    Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.

    Also in 5 projects that use this

  • nexuschainsSkill

    cross-linker

    Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.

    Also in 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-setup

    Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.

    Also in 5 projects that use this

  • bozhouDevSkill

    wiki-init

    Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.

    Also in 7 projects that use this

  • +1 more from nexuschains
  • +3 more from Ivy-Chen1999

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    When two sources contradict each other, set status: disputed, quote both locations and write an escalation.

    line 11
  2. Very specific:

    Update wiki/index.md and append one entry to wiki/log.md: date, the context/ commit that was ingested, the run id, pages created, updated …

    line 12
  3. Very specific:

    Run uv run harness wiki-lint.

    line 13
  4. Very specific:

    Never edit context/. Never delete a page without an answered escalation.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 38 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

Ingest into the wiki

  1. Find the work. Use the paths in prompt.md; when it names context as a whole, list what changed since the commit recorded in the last entry of wiki/log.md: git log --name-only <commit>..HEAD -- context/.
  2. For each changed source file, write or update wiki/sources/<slug>.md: type: source, raw with the context/ path, source_kind, and what the file contains, with line locators.
  3. For each fact or entity the source adds or changes, search wiki/index.md first. Update the existing page, or create one from templates/wiki/page.md. Never create a second page for the same thing. Keep one ingest to a handful of pages and list what remains in output/changes.md.
  4. When two sources contradict each other, set status: disputed, quote both locations and write an escalation. Do not pick a side.
  5. Update wiki/index.md and append one entry to wiki/log.md: date, the context/ commit that was ingested, the run id, pages created, updated and disputed.
  6. Run uv run harness wiki-lint; it must exit 0. Commit on the worktree branch, then write output/changes.md and result.json.

Never edit context/. Never delete a page without an answered escalation. Never copy a secret or personal data into a page.

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.