agentleFS
slogsdonslogsdon/skills-vault-knowledge/skills/ingest/SKILL.md

ingest

Skill0 starsChanged 3 months agoMITView on GitHub

Synthesize raw source material into the vault's Concepts wiki — turn a Clipping, article, transcript, or pasted source into a structured Concept page and register it in the index and log. Use when /ingest is invoked, when Shane says "ingest this", "add this to the wiki", "make a concept page from X", "process this clipping", or when /inbox-triage routes a source into Concepts. Do NOT use for raw capture (use /log), for polished writing (use /learned), or for surfacing links between existing notes (use /connect).

88 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • phanghonghaoSkill

    poster

    HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every Concept page MUST have, in order:

    line 18
  2. Very specific:

    Create: when the concept has no page.

    line 25
  3. Very specific:

    Read Context/Vault Schema.md (the governing contract) and resolve the source.

    line 32
  4. Distinctive:

    Follow Qwen Protocol with:

    line 34
  5. Very specific:

    Write the page (obsidian create for new, obsidian append under ## Update — <date> for existing).

    line 38
  6. Very specific:

    Update Inbox/vault-index.md and Inbox/vault-log.md per the contract.

    line 39
  7. Distinctive:

    Commit the vault (Post-write protocol below).

    line 40
  8. Distinctive:

    If Qwen is unavailable:

    line 44
  9. Very specific:

    Read the source and any related Concepts (obsidian read file='...').

    line 47
  10. Distinctive:

    After the writes, commit:

    line 55

“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “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

Skill: /ingest [source]

Turn one raw source into a durable Concept page in the vault, following Context/Vault Schema.md exactly. The output is a wiki page a future LLM can trust, not a summary dump.

Don't: overwrite an existing Concept's ## Shane's Take — append under ## Update — <date> instead. Don't skip the index/log updates — an ingest that isn't registered is invisible. Don't ingest transient Inbox/Clippings cross-references into the link graph.

Inputs

source is one of: a Clipping note name (obsidian read file='...'), a URL/article, a transcript, or pasted text. If ambiguous, ask which source before proceeding.

Contract (from Context/Vault Schema.md — read it first)

Every Concept page MUST have, in order:

## Shane's Take        ← mandatory, first, captured before synthesis. Never omit.
## Summary             ← concise, factual
## Key Points          ← 3–7 bullets
## Cross-references / Related   ← [[Concept Name]] wikilinks, bidirectional
  • Create when the concept has no page; Update (append ## Update — <date>) when it does — never silently overwrite.
  • On EVERY ingest, update both registry files (they live in Inbox/, not the vault root):
    • Inbox/vault-index.md → add/update - [[Page Name]] — one-line description
    • Inbox/vault-log.md → append - <date> | <source> | <concept> | <change summary>

Steps

  1. Read Context/Vault Schema.md (the governing contract) and resolve the source.
  2. Capture Shane's Take first — ask Shane for his angle in one or two lines, or lift his verbatim words if already present. Never synthesize over an empty Take.
  3. Follow Qwen Protocol with:
    • task: "Vault access (bash only, no MCP tools): obsidian search query='TERM' limit=10, obsidian read file='Note Name' (no .md), obsidian create name='Name' content='...'. Synthesize the source '[source]' into a Concepts page following the four-section format (Shane's Take / Summary / Key Points / Cross-references). Search existing Concepts and add bidirectional [[wikilinks]]."
    • skill: "ingest"
  4. Decide create vs. update by searching Concepts/ for an existing page on this concept.
  5. Write the page (obsidian create for new, obsidian append under ## Update — <date> for existing).
  6. Update Inbox/vault-index.md and Inbox/vault-log.md per the contract.
  7. Commit the vault (Post-write protocol below).

Fallback

If Qwen is unavailable:

  1. obsidian search query='[concept]' limit=10 to check for an existing Concept page.
  2. Read the source and any related Concepts (obsidian read file='...').
  3. Draft the four sections; get Shane's Take in his words before synthesizing the rest.
  4. obsidian create (new) or obsidian append (update under a dated heading).
  5. Append the Inbox/vault-index.md and Inbox/vault-log.md lines.
  6. Present the new/updated page path + the index/log deltas to Shane.

Post-write protocol

After the writes, commit:

VAULT="$HOME/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal"
git -C "$VAULT" add '<the note paths you wrote>' && git -C "$VAULT" commit -m "docs: ingest [source] → Concept [name]"

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.