agentleFS
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/wiki-ingest-source/SKILL.md

wiki-ingest-source

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

SOP for source page creation — write immutable source page capturing raw material, then update search index.

1 other project uses 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, 6 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create an immutable source page capturing raw research material (paper notes, web content, experimental data).

    line 10
  2. Distinctive:

    Before creating a source page, search the vault for existing sources covering the same material.

    line 15
  3. Distinctive:

    If vault_search returns a match with score > 8.0 for the source title, STOP and report the duplicate.

    line 16
  4. Distinctive:

    Search vault for existing source with similar title/content

    line 27
  5. Distinctive:

    If duplicate found → report and abort

    line 28
  6. Very specific:

    Write source page to sources/<slug>.md with frontmatter:

    line 29
  7. Very specific:

    Call vault_index (incremental) to make the page searchable

    line 40
  8. Distinctive:

    Immutable after creation: Never edit source pages.

    line 45

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

Create an immutable source page capturing raw research material (paper notes, web content, experimental data). Sources are never edited after creation — they preserve the original material.

HARD-GATE

<HARD-GATE> Before creating a source page, search the vault for existing sources covering the same material. If vault_search returns a match with score > 8.0 for the source title, STOP and report the duplicate. </HARD-GATE>

Tools

  • vault_search (deduplication check)
  • vault_index (post-creation index update)
  • CC file write (page creation)

Protocol

  1. Search vault for existing source with similar title/content
  2. If duplicate found → report and abort
  3. Write source page to sources/<slug>.md with frontmatter:
    ---
    type: source
    title: "<descriptive title>"
    created: <YYYY-MM-DD>
    origin: <url or citation>
    tags: [<relevant tags>]
    ---
  4. Body contains raw material (quotes, data, notes) — no synthesis
  5. Call vault_index (incremental) to make the page searchable
  6. Return path of created source

Source Page Rules

  • Immutable after creation. Never edit source pages.
  • Verbatim content. Preserve original wording, data, structure.
  • Attribution required. Origin field must trace back to the original.
  • No interpretation. Synthesis belongs in wiki pages, not sources.

Yield

Returns: { created: string, indexed: boolean }

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.