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

capture

Skill0 starsChanged 25 days agoMITView on GitHub

Record or update an open point (OP), claim (C) or decision (D) in the YAML registers of the knowledge base. Use when the user agrees to log a question, an assertion with its evidence, or a decision.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, brief and 8 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.
  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 4 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 6 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 6 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • LangChainSkill

    remember

    Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never strengthen a claim's evidence without citing the stronger source in history.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 55 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

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

Edit only artifacts/registers/{open_points,claims,decisions}.yaml. The .md views are generated (editing them is blocked).

  • New item — next free id (uv run python tools/ingest/query.py "SELECT max(id) FROM kb.reg_open_points", or reg_claims / reg_decisions; the first item of a register is OP-001 / C-001 / D-001). Fields: OP: id, title (≤140 ch), status: open, owner (TBD if unknown), text, impact, history: []. Claim: id, claim (one testable assertion), object, evidence (schema enum), source (path#Lx-Ly or SQL), contradicted_by, dependency, status: open, history: []. Decision: id (D-nnn), date, decision, rationale, ref.
  • Change to an existing item — do not rewrite text/claim. Set status / owner / priority, updated: <today>, and append to history one {date: <today>, note: <one line with citation>}. Resolving an OP = status: resolved + a decision item whose ref names the OP.
  • Never strengthen a claim's evidence without citing the stronger source in history.

Then run uv run python tools/kb/refresh.py (the hook may already have regenerated the views); fix any error it reports. Reply with one line per id touched. Nothing else.

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