aif-ingest
Skill0 starsChanged 7 months agoMITView on GitHub
Ingest a document into the vault knowledge base
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill
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
- Distinctive: line 14
When the user provides a document to ingest (URL, file path, or pasted content):
- Very specific: line 17
Create a source summary at vault/wiki/sources/<slug>.md with:
- Distinctive: line 22
Update existing concept/entity pages that the new source relates to
- Very specific: line 23
Add entry to vault/wiki/index.md
- Very specific: line 28
NEVER modify files in vault/raw/ after creation (immutable)
- Distinctive: line 29
ALWAYS add YAML frontmatter to wiki pages
- Distinctive: line 30
ALWAYS update the index
- Distinctive: line 31
ALWAYS log the operation
- Very specific: line 32
Use approved tags from vault/.vault/rules/tags.md
≈ “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.
Files
Vault Ingest
Telemetry (run first, silent):
aiframework-telemetry skill_invoked skill=aif-ingest 2>/dev/null || trueWhen the user provides a document to ingest (URL, file path, or pasted content):
- Save the raw content to
vault/raw/<slug>.md - Create a source summary at
vault/wiki/sources/<slug>.mdwith:- YAML frontmatter (title, type: source, date, tags)
- One-paragraph summary
- Key topics/sections
- Wikilinks to related concept pages
- Update existing concept/entity pages that the new source relates to
- Add entry to
vault/wiki/index.md - Log to
vault/wiki/log.md - 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
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
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.

