agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/wiki-vault/skills/knowledge-compilation/SKILL.md

knowledge-compilation

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Tactic for compiling research findings into vault pages — orchestrates page creation, updates, edge linking, and index maintenance. Minimum yield ≥3 page operations per invocation.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. yogsoth-ai/knowledge-structuring★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Deduplication first: Always search before creating.

    line 23
  2. Distinctive:

    Edges are first-class: Every new page should have at least one edge connecting it to the existing graph.

    line 24
  3. Distinctive:

    If incoming material cannot produce 3 operations, accumulate and defer.

    line 32
  4. Distinctive:

    When to create new pages vs update existing ones

    line 41
  5. Distinctive:

    Search vault for existing coverage of incoming topics

    line 44
  6. Distinctive:

    Run vault_lint (report mode) to verify no broken links introduced

    line 47
  7. Very specific:

    After compilation completes, trigger context-checkpoint to persist vault state changes to the context layer.

    line 51

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

Knowledge Compilation

Compile research findings into structured vault pages. Triggered after each strategy completes, or when CC judges accumulated information density warrants compilation.

Available SOPs

  • wiki-search — check for existing pages before creating duplicates
  • wiki-ingest-source — write immutable source pages
  • wiki-compile-page — create/update wiki pages with edges
  • wiki-add-edge — create typed relationships between pages
  • wiki-lint-fix — run lint in report mode at end

Guiding Principles

  • Assess before acting. Scan incoming material. Identify what's new vs what updates existing pages.
  • Deduplication first. Always search before creating. Near-duplicates should be merged, not added.
  • Edges are first-class. Every new page should have at least one edge connecting it to the existing graph. Orphans are failures.
  • Source immutability. Source pages capture raw material verbatim. Wiki pages synthesize and evolve.
  • Batch efficiency. Group related operations. Create all pages for a concept cluster, then wire edges, then index once.

Minimum Yield

<HARD-GATE> ≥3 page operations per invocation (any combination of: create page, update page, add edge). If incoming material cannot produce 3 operations, accumulate and defer. </HARD-GATE>

Execution Guidance

CC has full autonomy over:

  • Which SOPs to invoke and in what order
  • Whether to spawn a subagent for complex ingest decisions
  • How to partition material across pages
  • When to create new pages vs update existing ones

Typical flow (reference, not prescription):

  1. Search vault for existing coverage of incoming topics
  2. Decide page operations: new sources, new wiki pages, updates, edges
  3. Execute operations via SOPs
  4. Run vault_lint (report mode) to verify no broken links introduced

Context-Management Integration

After compilation completes, trigger context-checkpoint to persist vault state changes to the context layer.

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