agentleFS
minosinminosin/gtdbrain-claude-plugin/skills/setup/SKILL.md

setup

Skill0 starsChanged 37 days agoMITView on GitHub

Check that GTD Brain is connected and signed in, and walk the user through connecting if it is not. Use right after installing the plugin, when GTD Brain tools are missing, or when a tool answers with an authentication error.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 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.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the list_contexts tool with no arguments (a schema lookup.

    line 15
  2. Very specific:

    Claude Code (terminal): run /mcp, choose gtdbrain, and follow the sign-in prompt.

    line 30
  3. Distinctive:

    No GTD Brain account is needed in advance — signing in with a new email creates one.

    line 41
  4. Distinctive:

    Do not call any other GTD Brain tool from this skill.

    line 53
  5. Distinctive:

    Do not claim the sign-in tab will open from chat on its own.

    line 54
  6. Distinctive:

    Do not ask the user for an email code, password, token, or URL.

    line 55

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

GTD Brain setup

Diagnose the connection to the gtdbrain MCP server and give the user concrete next steps. This skill never opens a browser, never asks for credentials, and never invents an OAuth URL, device code, or token — sign-in is owned by the Claude client, not by this skill.

Procedure

  1. Call the list_contexts tool with no arguments (a schema lookup; on an account without a membership it answers with the membership notice, which still proves the connection).
  2. Branch on the result.

A — The call succeeds

Reply in one or two lines: GTD Brain is connected; the user can ask you to capture something, list next actions (optionally by context), review projects or Waiting For, or run /gtdbrain:weekly-review. If the contexts returned are only defaults and the board looks freshly seeded, mention that the starter cards can be archived whenever they like.

B — The tool is not available, or the call fails with 401 / "authentication required"

Tell the user, adapting to where they are:

  • Claude Code (terminal): run /mcp, choose gtdbrain, and follow the sign-in prompt. A browser tab opens on GTD Brain's sign-in page; enter an email, type the code that arrives, click Allow. If the tab never opens (e.g. over SSH), /mcp prints the URL to open by hand.
  • claude.ai, Claude Desktop, and Cowork: installing the plugin does not connect it. In the left sidebar, open Customize → Plugins → GTD Brain, go to the Connectors tab, and connect GTD Brain there. Then complete the same email-code sign-in. Do not send plugin users to Settings to add a custom connector: that creates a second, separate connector the plugin does not use.
  • Using GTD Brain without the plugin: Settings → Connectors → Add custom connector with https://mcp.gtdbrain.com/api/gtdbrain/v1/mcp. Custom connectors require a paid Claude plan.
  • No GTD Brain account is needed in advance — signing in with a new email creates one.

Then ask them to run /gtdbrain:setup again to confirm.

C — Any other error

Quote the error verbatim in one line, point to the guide at https://gtdbrain.com/connect/claude-code (Claude Code) or https://gtdbrain.com/connect/claude (other Claude surfaces), and offer admin@minosin.com for support. Stop there.

Rules

  • Do not call any other GTD Brain tool from this skill.
  • Do not claim the sign-in tab will open from chat on its own.
  • Do not ask the user for an email code, password, token, or URL.

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.