agentleFS
Sign inStart free
minosinminosin/gtdbrain-claude-plugin/skills/capture/SKILL.md

capture

Skill0 starsChanged 37 days agoMITView on GitHub

Add things to the user's to-do list (their GTD Brain Inbox). Use when the user says "add … to my list", "put … on my to-do list", "remind me to…", "I need to…", "I have to…", "don't let me forget…", "capture", or lists several things on their mind. Not for TODO comments in code.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, ingest 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

  • JaimeGBASkill

    ingest

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

    Also in 8 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 4 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

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

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 0

    Distinctive

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

    If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

    line 8
  2. Very specific:

    If the text holds several distinct items (separate lines, "and", commas between unrelated things), call capture once per item, each with a …

    line 10
  3. Very specific:

    If $ARGUMENTS is empty, ask what to capture — invite the user to empty their head and list everything, then capture each item.

    line 13
  4. Very specific:

    Do not clarify, prioritise, or assign contexts now.

    line 15

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

Capture "$ARGUMENTS" to the user's GTD Brain Inbox. If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

  • If the text holds several distinct items (separate lines, "and", commas between unrelated things), call capture once per item, each with a short, specific title. Keep any detail that does not belong in the title in notes.
  • If $ARGUMENTS is empty, ask what to capture — invite the user to empty their head and list everything, then capture each item.
  • Do not clarify, prioritise, or assign contexts now; capture goes to the Inbox raw. Clarifying happens in /gtdbrain:inbox-zero.
  • Confirm with the created titles in one line, and if any item obviously needs several steps, offer to turn it into a project with a first next action.

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