agentleFS
juanitourquizajuanitourquiza/shipframe/skills/wiki-forge/SKILL.md

wiki-forge

Skill4 starsChanged 21 days agoMITView on GitHub

Convert documents into an interconnected LLM wiki using the Karpathy wiki pattern and project conventions.

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 11 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating anything, understand the project.

    line 28
  2. Distinctive:

    If there is genuine ambiguity, ask only what is essential:

    line 30
  3. Distinctive:

    Create the folder structure (see Architecture below).

    line 38
  4. Very specific:

    Create empty wiki/index.md and wiki/log.md.

    line 45
  5. Very specific:

    Read .claude/wiki-conventions.md.

    line 88
  6. Very specific:

    Read the source in full from raw/.

    line 93
  7. Distinctive:

    Create or update wiki pages:

    line 97
  8. Very specific:

    Always one page in sources/ with wikilinks to the raw files it covers.

    line 98
  9. Distinctive:

    If a page already exists: extend with new content, do not duplicate.

    line 100
  10. Distinctive:

    When done, run LINT.

    line 130
  11. Very specific:

    Follow the delegation instructions in .claude/wiki-conventions.md exactly.

    line 134
  12. Very specific:

    Read .claude/wiki-conventions.md before running any check.

    line 143
  13. Distinctive:

    Density: all thematic pages with at least 8 wikilinks distributed throughout the body.

    line 153
  14. Distinctive:

    Incoming links: all thematic pages with at least 5 incoming links.

    line 155
  15. Distinctive:

    Add links from related pages if needed.

    line 156
  16. Very specific:

    Raw linked: all files in raw/ referenced from at least one page in sources/.

    line 157
  17. Distinctive:

    If there are multiple vaults:

    line 168
  18. Distinctive:

    Create inter-vault links or propose consolidation.

    line 172
  19. Very specific:

    Do not mix the raw/ folders of different projects.

    line 173

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

Transforms raw documents into living knowledge wikis.

Core idea: the LLM reads sources once, extracts knowledge, and organizes it into interlinked markdown pages that grow richer with each new source. Knowledge accumulates — it is not re-derived on every query.


The 4 operations

SETUP → INGEST (batch) → LINT → repeat. For queries, use /wiki-query.


SETUP — Create a new vault

Before creating anything, understand the project. If the user provides material without explanation, infer from the content — acting beats asking. If there is genuine ambiguity, ask only what is essential:

  • Domain (what is this about?)
  • Source types (what material will be ingested?)
  • Language (detect from the material if not specified)

With that:

  1. Create the folder structure (see Architecture below).
  2. Move the user's sources into raw/.
  3. Generate WIKI.md at the root — use templates/wiki/wiki-md-template.md substituting all {{}} placeholders.
  4. Generate .claude/wiki-conventions.md — use templates/wiki/conventions-template.md substituting {{VAULT_NAME}} and {{LANGUAGE}} with the vault's values.
  5. Create empty wiki/index.md and wiki/log.md.

Tip: For a guided setup that asks all the right questions, use /wiki-init instead.

Vault architecture

vault-name/
├── CLAUDE.md                    ← Orientation: structure, sources, skills
├── .claude/
│   └── wiki-conventions.md     ← Wiki standards: format, language, wikilinks
├── raw/                        ← Original sources — IMMUTABLE
│   └── [user structure]
├── wiki/
│   ├── index.md                ← Master catalog
│   ├── log.md                  ← Operation history
│   ├── logs/                   ← One file per sync (/wiki-sync)
│   ├── sources/                ← One summary per ingested source
│   └── [categories]/           ← Subdirectories adapted to the domain

Detecting source structure

Analyze how the sources are organized before ingesting:

Corpus structuresources/ granularity
Course with modules and lessonsOne source page per module
Periodic meetingsOne page per meeting or sprint
Slack / Discord channelOne page per thread or topic
Collection of articles / PDFsOne page per document
Standalone YouTube videosOne page per video
Loose notesGroup by topic or one per note

Each sources/ page must include wikilinks to all raw files it covers — this connects the originals to the wiki graph.


INGEST — Process sources

Step 0 — Load conventions

Read .claude/wiki-conventions.md. All pages created or modified in this operation must follow those conventions without exception.

Steps

  1. Read the source in full from raw/.
  2. Classify the type (transcript, report, meeting, article, notes...).
  3. Extract domain entities — the content dictates what to extract: concepts, techniques, tools, people, decisions, data, relationships.
  4. Create or update wiki pages:
    • Always one page in sources/ with wikilinks to the raw files it covers.
    • Thematic pages in the corresponding categories.
    • If a page already exists: extend with new content, do not duplicate.
  5. Link densely with [[wikilinks]] — follow the rules in wiki-conventions.md (minimum count, distribution, no broken links).
  6. Update wiki/index.md.
  7. Log in wiki/log.md:
    ## [YYYY-MM-DD] ingest | Source name
    - Pages created: X
    - Pages updated: Y
    - Entities extracted: brief list

Rules by source type

  • Transcripts (YouTube, courses, podcasts): clean filler words. Extract logical structure, not temporal. Preserve practical examples.
  • Meetings: preserve who said what if relevant. Extract decisions, action items, and context.
  • Reports / PDFs: respect the document structure. Extract quantitative data, conclusions, recommendations.
  • Web articles: distinguish facts from opinions. Record author, date, and URL.
  • User notes: high-priority primary source. Integrate respecting the original intent.

Batch ingest

  1. List everything in raw/.
  2. Order: chronological, by complexity, or by conceptual dependencies (basics first so foundational concepts exist before advanced ones).
  3. Process one at a time, updating index and log after each.
  4. When done, run LINT.

Delegating to subagents

Follow the delegation instructions in .claude/wiki-conventions.md exactly. Include all 4 mandatory elements in each subagent prompt.


LINT — Maintenance

Step 0 — Load conventions

Read .claude/wiki-conventions.md before running any check.

Checklist (run all and report concrete numbers)

  1. Frontmatter: 100% of pages with the exact 5 fields defined in wiki-conventions.md. Fix any that fail.
  2. Language: 100% of pages in the language defined in wiki-conventions.md. Fix any in a different language.
  3. Ghost links: 0 broken wikilinks. List all [[wikilink]] targets and verify they exist as .md files. Create missing pages or fix links.
  4. Density: all thematic pages with at least 8 wikilinks distributed throughout the body. Fix those below threshold.
  5. Incoming links: all thematic pages with at least 5 incoming links. Add links from related pages if needed.
  6. Raw linked: all files in raw/ referenced from at least one page in sources/.
  7. Orphans: wiki pages with no incoming links — connect them or delete them.
  8. Gaps: concepts mentioned repeatedly without their own page — create them.

Log results in wiki/log.md with the check numbers.


MERGE — Connect wikis

If there are multiple vaults:

  1. List the wikis and their domains.
  2. Identify shared entities.
  3. Create inter-vault links or propose consolidation.
  4. Do not mix the raw/ folders of different projects.

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.