agentleFS
TracebrainTracebrain/mcp/skills/capture/SKILL.md

capture

Skill1 starsChanged 31 days agoMITView on GitHub

Turn something the user just said they would do, or that somebody owes them, into a task on the right person's page. Use when they say they promised something, need to remember to do something for somebody, want to add a to-do, or when a conversation ends with an action and they ask you to note it down.

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

  • 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

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

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the line back before writing it when you had to rephrase much.

    line 21

“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

Write that promise down

One line onto the Tracebrain task list, under the person it is owed to or by.

Order

  1. find_people to turn the name into a note stem. A task belongs to somebody already in the vault; there is no tool that adds a person, and guessing a stem gets a refusal rather than a new page.
  2. add_task with that stem and one line in the imperative - "send Olena the deck", not "I said I'd probably get the deck over to Olena at some point".
  3. Say where it landed, so the user can see it on the Tasks screen.

What to say

Read the line back before writing it when you had to rephrase much. A promise recorded in words the user would not recognise is a promise they will not act on.

Rules

  • The same task twice is refused, not duplicated. That is the vault protecting itself; do not work around it by rewording the line.
  • One promise, one task. "Send the deck and book the room" is two.
  • Only what the user said. A task invented from something a model inferred is a promise nobody made.
  • No passwords, codes or card numbers in a task. They stay in the conversation; the server refuses a line that looks like one anyway.

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.