agentleFS
Sign inStart free
natalinionatalinio/project-second-brain/.claude/skills/ingest/SKILL.md

ingest

Skill0 starsChanged 26 days agoMITView on GitHub

Bring new material from inbox/ into the knowledge base — triage into source/, parse, refresh — and report what it confirms, contradicts or extends. Use when files were dropped into inbox/.

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

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

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Delta, bounded: Run graph.py about on the 3–5 main objects of the new material and keep only the sections of the new note.

    line 17
  2. Very specific:

    Never edit the body of a knowledge/extracted/ note (hook-enforced): corrections and syntheses go to knowledge/curated/.

    line 24

“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

Input: $ARGUMENTS (the text typed after the command).

  1. Triage. Classify each file with the table in inbox/README.md; move it to that source/ subfolder (never edit the original); add a row to source/MANIFEST.md in that section's format.
  2. Parse. Office/PDF documents → uv run python tools/ingest/extract_embedded.py --only "<name>", then uv run python tools/ingest/parse_docs.py --only "<name>"; .eml → uv run python tools/ingest/parse_email.py; spreadsheets/CSV → uv run python tools/ingest/build_inventory.py. Images → transcribe into knowledge/curated/diagrams/ (Mermaid + prose, origin: curated). Content that has no file (a chat, a call) → a curated note in knowledge/curated/<kind>/, evidence: verbal, attributed and dated.
  3. Refresh. uv run python tools/kb/refresh.py; fix lint errors in what you wrote.
  4. Delta, bounded. Run graph.py about on the 3–5 main objects of the new material and keep only the sections of the new note. Report at most 10 bullets: each new fact → confirms / contradicts / extends an existing claim, OP or decision (with ids), cited path#Lx-Ly. Do not summarise the whole document.
  5. Propose register changes (close/narrow OP, new claim, new OP, decision, contradiction) as a short list. Apply them with /capture only after the user agrees. New recurring names → propose aliases for tools/kb/entities.yaml.

Never edit the body of a knowledge/extracted/ note (hook-enforced): corrections and syntheses go to knowledge/curated/.

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.

Check your setup, free