agentleFS
Sign inStart free
fakechrisfakechris/obsidian_vault_pipeline/skills/capture-drop/SKILL.md

capture-drop

Skill165 starsChanged 4 months agoApache-2.0View on GitHub

Drop bot/agent captures only into safe inbox folders (50-Inbox/00-Capture or Clippings). Never write crystal, ledgers, or rewrite Source notes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Write ordinary markdown notes under those folders only.

    line 15
  2. Very specific:

    Do not write under .ovp/crystal, evolution ledgers, or other .ovp/ append-only product state

    line 19
  3. Distinctive:

    Do not hand-edit Crystal / ledgers

    line 20
  4. Very specific:

    Do not rewrite Source notes.

    line 21
  5. Distinctive:

    Do not commit secrets, API keys, or raw provider env files into the vault or this repo

    line 22
  6. Very specific:

    Prefer Involute INV ids and ovp:// claim/source/theme pointers in agent-data instead of copying Crystal prose into local agent scratch.

    line 26

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

OVP Capture Drop

Safe drop-folder rules for bots and agents writing into the operator vault.

Drop here only

  • 50-Inbox/00-Capture/ — preferred for tagged/inbox captures
  • Clippings/ — optional alternate for clip-style notes

Write ordinary markdown notes under those folders only. Intake (ovp2 daily / pipeline) normalizes them into 50-Inbox/01-Raw/ and onward.

Never do this

  • Do not write under .ovp/crystal, evolution ledgers, or other .ovp/ append-only product state
  • Do not hand-edit Crystal / ledgers
  • Do not rewrite Source notes; use product commands (ovp2 …) for pipeline mutations
  • Do not commit secrets, API keys, or raw provider env files into the vault or this repo

Pointers over copies

Prefer Involute INV ids and ovp:// claim/source/theme pointers in agent-data instead of copying Crystal prose into local agent scratch.

After dropping

Operators process captures via the daily loop (ovp2 daily --vault-root …). Agents should not invent alternate write paths into Reader/Crystal.

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