agentleFS
Sign inStart free
protonium-labsprotonium-labs/axiomcore-plugin/skills/ingest/SKILL.md

ingest

Skill3 starsChanged 3 months agoMITView on GitHub

Process raw files from vault/sources/ into linked wiki pages. Actions - all (every unprocessed source), file (one specific source), overview.

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

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

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 4

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

    If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.

    line 12
  2. Distinctive:

    If the action was unknown, say so first, then show the table.

    line 28
  3. Distinctive:

    Update existing pages where the topic exists.

    line 39
  4. Very specific:

    Add YAML frontmatter (tags, created, updated, source) and [[wiki links]] to every related page.

    line 40
  5. Very specific:

    Update vault/index.md with new pages.

    line 50
  6. Distinctive:

    All pages must pass markdownlint.

    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

Task

Execute the requested action: $ARGUMENTS

Calling rule: /ingest <action> <arguments>.

If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.

If action is empty

Describe this skill: its purpose and the actions table from "overview". Do not execute anything.

If action is "overview" (or unknown)

ArgumentAction
allProcess every unprocessed file in vault/sources/
file <name>Process one specific source file
overviewThis table

If the action was unknown, say so first, then show the table.

If action is "all" or "file"

  1. Scope:
    • all: list vault/sources/ and compare against vault/log.md ingest entries to find unprocessed files. Large batches: one source at a time, report progress.
    • file <name>: match the name in vault/sources/; if missing or empty, list the folder and ask.
  2. Read each source fully. PDFs, images, transcripts, articles alike.
  3. Integrate, don't just summarize, per source:
    • Update existing pages where the topic exists; create new pages only for genuinely new topics (one topic per page).
    • Add YAML frontmatter (tags, created, updated, source) and [[wiki links]] to every related page. A single source may touch 10-15 pages.
    • Route by content: user-related → vault/me/, project-related → vault/projects/<name>/, general knowledge → vault/knowledge/.
    • Flag contradictions explicitly in the page and in the report; never silently overwrite.
  4. Never modify the source file itself (CLAUDE.md hard rule).

After any action

  • One log entry per source: ## [YYYY-MM-DD HH:MM] /ingest | <source> -> pages touched.
  • Update vault/index.md with new pages.
  • Report: sources processed, pages created/updated, contradictions flagged.

Notes

  • All pages must pass markdownlint.

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