agentleFS
sp1esp1e/claude-skills/gsd-config/SKILL.md

gsd-config

Skill1 starsChanged 31 days agoMITView on GitHub

Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile

  • Installs packages

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    If it is --advanced: strip the flag, execute settings-advanced workflow

    line 45
  2. Very specific:

    If it is --integrations: strip the flag, execute settings-integrations workflow

    line 46
  3. Very specific:

    If it starts with --profile: extract the profile name (remainder after --profile), then:

    line 47
  4. Very specific:

    Pre-flight check (#2439): verify gsd-sdk is on PATH via command -v gsd-sdk.

    line 48
  5. Very specific:

    If absent, emit the install hint Install GSD via 'npm i -g get-shit-done' and stop — do NOT invoke gsd-sdk directly (avoids the opaque …

    line 49
  6. Very specific:

    Run: gsd-sdk query config-set-model-profile <profile-name> --raw and display the output verbatim.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 4 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
<objective> Configure GSD settings interactively with a single consolidated command.

Mode routing:

  • default (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow
  • --advanced: Power-user knobs (planning tuning, timeouts, branch templates, cross-AI execution) → settings-advanced workflow
  • --integrations: Third-party API keys, code-review CLI routing, agent-skill injection → settings-integrations workflow
  • --profile <name>: Switch model profile (quality|balanced|budget|inherit) → set-profile (inline)</objective>
<routing>
FlagActionWorkflow
(none)Interactive 5-question common-case config promptsettings
--advancedPower-user knobs: planning, execution, discussion, cross-AI, git, runtimesettings-advanced
--integrationsAPI keys (Brave/Firecrawl/Exa), review CLI routing, agent skillssettings-integrations
--profile <name>Switch model profile without interactive promptgsd-sdk config-set-model-profile
</routing>

<execution_context> @$HOME/.claude/get-shit-done/workflows/settings.md @$HOME/.claude/get-shit-done/workflows/settings-advanced.md @$HOME/.claude/get-shit-done/workflows/settings-integrations.md </execution_context>

<context> Arguments: $ARGUMENTS

Parse the first token of $ARGUMENTS:

  • If it is --advanced: strip the flag, execute settings-advanced workflow
  • If it is --integrations: strip the flag, execute settings-integrations workflow
  • If it starts with --profile: extract the profile name (remainder after --profile), then:
    1. Pre-flight check (#2439): verify gsd-sdk is on PATH via command -v gsd-sdk. If absent, emit the install hint Install GSD via 'npm i -g get-shit-done' and stop — do NOT invoke gsd-sdk directly (avoids the opaque command not found: gsd-sdk failure).
    2. Run: gsd-sdk query config-set-model-profile <profile-name> --raw and display the output verbatim.
  • Otherwise: execute settings workflow (no argument needed)</context>
<process> 1. Parse the leading flag (if any) from $ARGUMENTS. 2. Load and execute the appropriate workflow end-to-end, or run the inline SDK command for --profile. 3. Preserve all workflow gates from the target workflow. </process>

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.