agentleFS
evergonlabsevergonlabs/aiframework/.claude/skills/aif-ingest/SKILL.md

aif-ingest

Skill0 starsChanged 7 months agoMITView on GitHub

Ingest a document into the vault knowledge base

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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. Distinctive:

    When the user provides a document to ingest (URL, file path, or pasted content):

    line 14
  2. Very specific:

    Create a source summary at vault/wiki/sources/<slug>.md with:

    line 17
  3. Distinctive:

    Update existing concept/entity pages that the new source relates to

    line 22
  4. Very specific:

    Add entry to vault/wiki/index.md

    line 23
  5. Very specific:

    NEVER modify files in vault/raw/ after creation (immutable)

    line 28
  6. Distinctive:

    ALWAYS add YAML frontmatter to wiki pages

    line 29
  7. Distinctive:

    ALWAYS update the index

    line 30
  8. Distinctive:

    ALWAYS log the operation

    line 31
  9. Very specific:

    Use approved tags from vault/.vault/rules/tags.md

    line 32

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

Vault Ingest

Telemetry (run first, silent):

aiframework-telemetry skill_invoked skill=aif-ingest 2>/dev/null || true

When the user provides a document to ingest (URL, file path, or pasted content):

  1. Save the raw content to vault/raw/<slug>.md
  2. Create a source summary at vault/wiki/sources/<slug>.md with:
    • YAML frontmatter (title, type: source, date, tags)
    • One-paragraph summary
    • Key topics/sections
    • Wikilinks to related concept pages
  3. Update existing concept/entity pages that the new source relates to
  4. Add entry to vault/wiki/index.md
  5. Log to vault/wiki/log.md
  6. Report: "Ingested <title>. Updated N existing pages."

Rules

  • NEVER modify files in vault/raw/ after creation (immutable)
  • ALWAYS add YAML frontmatter to wiki pages
  • ALWAYS update the index
  • ALWAYS log the operation
  • Use approved tags from vault/.vault/rules/tags.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.