gsd-config
Skill1 starsChanged 58 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
- sp1e/claude-skillsedited, first seen Oct 12, 2026
- open-gsd/get-shit-done-reduxedited, first seen Oct 8, 2026
- open-gsd/gsd-coreedited, first seen Sep 2, 2026
- ZaneL1u/cloud-cli-proxyedited, first seen May 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- open-gsd/get-shit-done-redux★ 11k75% same
- open-gsd/gsd-core★ 11k75% same
- ZaneL1u/cloud-cli-proxy★ 5748% same
- sp1e/claude-skills★ 173% same
Wrote their own version · 0
None found.
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 repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-mattSkill
- banner-designSkill
- brandSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- designSkill
- design-systemSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- gsd-add-testsSkill
- gsd-ai-integration-phaseSkill
- gsd-audit-fixSkill
- gsd-audit-milestoneSkill
- gsd-audit-uatSkill
- gsd-autonomousSkill
- gsd-captureSkill
- gsd-cleanupSkill
- gsd-code-reviewSkill
- gsd-complete-milestoneSkill
- gsd-debugSkill
- gsd-discuss-phaseSkill
- gsd-docs-updateSkill
- gsd-eval-reviewSkill
- gsd-execute-phaseSkill
- gsd-exploreSkill
- gsd-extract-learningsSkill
- gsd-fastSkill
- gsd-forensicsSkill
- gsd-graphifySkill
- gsd-healthSkill
- gsd-helpSkill
- gsd-importSkill
- gsd-inboxSkill
- gsd-ingest-docsSkill
- gsd-managerSkill
- gsd-map-codebaseSkill
- gsd-mempalace-captureSkill
- gsd-mempalace-recallSkill
- gsd-milestone-summarySkill
- gsd-mvp-phaseSkill
- gsd-new-milestoneSkill
- gsd-new-projectSkill
- gsd-nextSkill
- gsd-ns-contextSkill
- gsd-ns-ideateSkill
- gsd-ns-manageSkill
- gsd-ns-projectSkill
- gsd-ns-reviewSkill
- gsd-ns-workflowSkill
- gsd-onboardSkill
- gsd-pause-workSkill
- gsd-phaseSkill
- gsd-plan-phaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
If it is --advanced: strip the flag, execute settings-advanced workflow
- Very specific: line 38
If it is --integrations: strip the flag, execute settings-integrations workflow
- Very specific: line 39
If it starts with --profile: extract the profile name (remainder after --profile), then:
- Very specific: line 40
Verify gsd-tools is on PATH via command -v gsd-tools.
- Very specific: line 41
Run: gsd-tools query config-set-model-profile <profile-name> --raw and display the output verbatim.
“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.
Files
<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>| Flag | Action | Workflow |
| (none) | Interactive 5-question common-case config prompt | settings |
| --advanced | Power-user knobs: planning, execution, discussion, cross-AI, git, runtime | settings-advanced |
| --integrations | API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills | settings-integrations |
| --profile <name> | Switch model profile without interactive prompt | gsd-tools query config-set-model-profile |
</routing><execution_context> @/home/tony/.config/opencode/gsd-core/workflows/settings.md @/home/tony/.config/opencode/gsd-core/workflows/settings-advanced.md @/home/tony/.config/opencode/gsd-core/workflows/settings-integrations.md </execution_context>
<context>
Arguments: $ARGUMENTSParse 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:- Verify
gsd-toolsis on PATH viacommand -v gsd-tools; if absent, emit the install hintInstall GSD via 'npm i -g @opengsd/gsd-core'and stop. - Run:
gsd-tools query config-set-model-profile <profile-name> --rawand display the output verbatim.
- Verify
- 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>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
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.