agentleFS
TrueHOOHATrueHOOHA/LLM-Wiki/.agents/skills/llm-wiki-ingest/SKILL.md

llm-wiki-ingest

Skill22 starsChanged 4 months agoApache-2.0View on GitHub

Ingest a newly provided raw source into the LLM Wiki OKF bundle. Use whenever the operator asks to add a source to the wiki, process a file under raw/sources or raw/assets, summarize and file an article/paper/transcript, or mentions ingestion, importing sources, or updating the wiki from a document.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gavishap/omnia-vault★ 53same name
    2. dotlabshq/crux★ 4same name

    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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Immutable raw files: Never edit, rename, move, or delete any file under raw/.

    line 17
  2. Very specific:

    Wiki ownership: Create/update pages only under wiki/ (unless operator explicitly overrides).

    line 18
  3. Very specific:

    Append-only log: Only append a new date-grouped entry to wiki/log.md.

    line 19
  4. Distinctive:

    If text references images/assets, read those after the main text.

    line 27
  5. Distinctive:

    Discuss key takeaways with operator: before framing final extraction.

    line 28

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

LLM Wiki Ingest Skill

Purpose

Integrate a newly provided raw source into the wiki while preserving raw-source immutability and maintaining index/log bookkeeping. The wiki is an OKF v0.1 bundle (see SPEC.md); wiki/ is the bundle root.

Preconditions (must pass before edits)

  1. The operator explicitly requested ingestion.
  2. The source file exists at raw/sources/<file> or raw/assets/<file>.
  3. The workflow will not modify anything under raw/.

Guardrails

  • Immutable raw files: Never edit, rename, move, or delete any file under raw/.
  • Wiki ownership: Create/update pages only under wiki/ (unless operator explicitly overrides).
  • Append-only log: Only append a new date-grouped entry to wiki/log.md; never rewrite or reorder prior entries.
  • Index freshness: Any wiki page change in this workflow requires wiki/index.md to be rebuilt before completion.
  • OKF conformance: Created/updated pages must satisfy OKF §9 (parseable frontmatter with non-empty type) and the producer conventions in AGENTS.md § Page Types & Conventions.
  • Obsidian wikilinks: Internal note-to-note links use Obsidian wikilinks ([[note]] / [[note|Display]]), resolving by file basename or frontmatter aliases. Standard markdown links are used ONLY for external URLs (https://…). See AGENTS.md § Cross-linking.
  • Single source of truth: The schema is defined in AGENTS.md. This skill enforces it; it never re-defines page types, frontmatter, or sections inline.

Required Step Order (exact)

  1. Read the raw source from raw/sources/ or raw/assets/.
    • If text references images/assets, read those after the main text.
  2. Discuss key takeaways with operator before framing final extraction.
    • Minimal prompt:
      • "I summarized the source. What should I emphasize?"
      • "Any specific connections to existing entities/concepts you want prioritized?"
      • "What should be de-emphasized or deferred?"
  3. Write source summary page in wiki/sources/ using filename YYYY-MM-DD--source-title-slug.md, following AGENTS.md § Source Pages. Set frontmatter resource to the raw source path (e.g. raw/sources/file.pdf); set title, description, tags, created, timestamp (today).
  4. Update/create entity pages in wiki/entities/ for concrete things mentioned, following AGENTS.md § Entity Pages. Use Obsidian wikilinks ([[note]] or [[note|Display]]) for cross-links and # Citations entries — the link target is the note's basename or one of its aliases. When updating an existing entity page from this source, increment its source_count by 1 and bump timestamp to today; when creating a new page, set source_count: 1.
  5. Update/create concept pages in wiki/concepts/ for abstract ideas mentioned, following AGENTS.md § Concept Pages, applying the same source_count increment and timestamp bump rule as step 4.
  6. Rebuild wiki/index.md following the Canonical rebuild procedure in AGENTS.md § Update Rules for Special Files (wiki/index.md): scan every .md under wiki/entities/, wiki/concepts/, wiki/sources/, and wiki/syntheses/ (never wiki/templates/), read each page's frontmatter, and rewrite the five sections (Entities, Concepts, Sources, Syntheses, Statistics) as bullet lists (* [[note-name|Title]] - description), preserving the okf_version: "0.1" frontmatter. The index must list exactly the pages that exist on disk.
  7. Append to wiki/log.md a single new date-grouped entry — newest first, never edit or reorder prior entries (OKF §7).
    • Heading: ## YYYY-MM-DD
    • Bullets: * **Ingest**: <Source Title> — <one-line summary of what was created/updated>., * **Pages touched**: <list>., * **Notes**: ..., * **Open questions**: ...

Done Gate (verify before reporting done)

  • Source page exists in wiki/sources/ and complies with its type contract in AGENTS.md § Source Pages (frontmatter has non-empty type plus title/description/resource/tags/timestamp; all H1 sections present).
  • Every entity/concept page created or updated complies with its type contract in AGENTS.md (Entity Pages / Concept Pages).
  • No legacy fields reintroduced (updated, source_path).
  • Internal links are Obsidian wikilinks ([[…]]); standard markdown links appear only for external URLs. No bundle-relative /path markdown links to internal notes.
  • Every [[wikilink]] in created/updated pages resolves to a page on disk (basename or aliases match), OR is an intentional not-yet-written reference (OKF §5.3 tolerates the latter; note any such links).
  • wiki/index.md rebuilt per the Canonical rebuild procedure and lists every page touched in this ingest (no phantom entries, no missing entries).
  • wiki/log.md has a newly appended ## YYYY-MM-DD ingest entry in the OKF §7 date-grouped format above.

Path Handling Rules

  • Input source roots: raw/sources/, raw/assets/.
  • Output summary root: wiki/sources/.
  • Entity updates: wiki/entities/.
  • Concept updates: wiki/concepts/.
  • Required global bookkeeping files: wiki/index.md, wiki/log.md.

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.