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

inbox-zero

Skill0 starsChanged 37 days agoMITView on GitHub

Sort the user's GTD Brain Inbox to zero, one item at a time. Use when they say "sort my to-do list", "clean up my list", "go through my GTD inbox", or want to clarify, triage, or empty their inbox.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 1

    1. alz-ahm/gtdbrain-claude-plugin★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 3

    1. GTMify/aigtm★ 25same name
    2. composio-community/support-skills★ 18same name
    3. TelosTechnology/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

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

    Call list_columns to get the column ids, then list_cards with the Inbox column id.

    line 9
  3. Distinctive:

    Wait for the user's answer before acting on each card.

    line 19
  4. Very specific:

    When the Inbox is empty, summarise what changed and suggest /gtdbrain:what-now.

    line 20

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

Process the user's GTD Brain Inbox to zero, one card at a time. If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

  1. Call list_columns to get the column ids, then list_cards with the Inbox column id.
  2. Take the cards oldest first. For each, state the title and ask what it really is, then act with a tool:
    • one step → phrase it verb-first, move_card to Next Actions, then update_card with a context if the user gives one (list_contexts shows the valid ids);
    • more than one step → create_card a project in Projects and create_card its first next action in Next Actions, then archive_card the raw Inbox card;
    • waiting on someone → move_card to Waiting For, then update_card with who and since;
    • a someday idea → move_card to Someday/Maybe;
    • done or no longer matters → archive_card.
  3. Wait for the user's answer before acting on each card; never batch-decide for them.
  4. When the Inbox is empty, summarise what changed and suggest /gtdbrain:what-now.

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