agentleFS
pqmcgillpqmcgill/family/.claude/skills/capture/SKILL.md

capture

Skill0 starsChanged 5 months agoMITView on GitHub

Use when the user drops a quick note, voice transcript, or mid-day update outside a check-in — "capture this", "add this", "quick note", "grabbed groceries" — anything that should be recorded now without running the full nightly or weekly session.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, 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.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 9 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

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 5 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 2

    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:

    If interpreting it needs current state (e.g.

    line 18
  2. Distinctive:

    Not a mini check-in: don't review neglect flags, don't ask about the day, don't prompt for pulses.

    line 33
  3. Distinctive:

    Not a place to skip confirmation because the note "is obvious."

    line 35

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

Quick Capture

Minimal flow — no ritual, no review, no pulse. Same hard rules as the nightly check-in skill: read the "Hard rules" and "Red flags" sections of .claude/skills/checkin/SKILL.md FIRST and apply all of them identically (CLI only; full batch then confirm then write; never guess facts; aliases only; every write carries --source capture or --source transcript).

Flow

  1. Take the user's note or transcript.
  2. If interpreting it needs current state (e.g. "mark the towels done" needs the week-entry id), run ./bin/fam --source capture checkin — never guess ids, never assume an item is new when it might map to existing state.
  3. Propose the extracted changes as one batch, with exact commands. Unknown people → propose fam person add. Ambiguity → ask.
  4. On confirmation: execute the writes; store the raw input: ./bin/fam --source capture journal add --session capture --kind transcript --text "..." (verbatim input) or --kind summary (short notes you've restated).
  5. Echo the WROTE lines back as confirmation. Done — exit. No pulse, no review, no "while we're at it."

What capture is NOT

  • Not a mini check-in: don't review neglect flags, don't ask about the day, don't prompt for pulses.
  • Not a place to skip confirmation because the note "is obvious."

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.