agentleFS
Sign inStart free
jzhao234jzhao234/big-brain/skills/codex/capture/SKILL.md

capture

Skill1 starsChanged 31 days agoMITView on GitHub

Quickly capture a thought, fact, idea, or link into the user's Big Brain. Use when the user asks to remember, note down, add to the brain/inbox, or explicitly invokes $capture.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, brief and 9 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 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

  • 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

  • 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

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

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 4

    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 the user supplies content, lightly clean it without changing meaning and run big-brain capture "<text>".

    line 11
  2. Distinctive:

    If the user supplies no content, capture the most recent clearly noteworthy decision, fact, or idea from the conversation.

    line 13
  3. Distinctive:

    If it clearly belongs to an existing active project, prefer appending it to that project's Notes/Log through an available Big Brain tool.

    line 15
  4. Distinctive:

    If it is actionable, suggest converting it into a project task.

    line 19
  5. Distinctive:

    Never capture secrets, access keys, passwords, tokens, private keys, or raw sensitive data.

    line 22

“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

Capture to Big Brain

Resolve the vault through big-brain; do not hardcode its location. Capture first and organize later.

  1. If the user supplies content, lightly clean it without changing meaning and run big-brain capture "<text>".
  2. If the user supplies no content, capture the most recent clearly noteworthy decision, fact, or idea from the conversation. State exactly what you chose.
  3. If it clearly belongs to an existing active project, prefer appending it to that project's Notes/Log through an available Big Brain tool. If only the CLI is available and cannot append arbitrary sections, capture it to the inbox rather than performing a risky rewrite.
  4. If it is actionable, suggest converting it into a project task; do not add the task unless requested or the user already asked to record the action.

Never capture secrets, access keys, passwords, tokens, private keys, or raw sensitive data. Big Brain writes may auto-commit and auto-push, so do not make a second manual commit for the same write.

Confirm in one line what was captured and where. Do not add a report around it.

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.

Reviews can't be read right now.

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