gsd-surface
Skill1 starsChanged 57 days agoMITView on GitHub
Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
- Installs packages
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- 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 versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- open-gsd/get-shit-done-redux★ 11k66% same
- open-gsd/gsd-core★ 11k66% same
- ZaneL1u/cloud-cli-proxy★ 5755% 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-configSkill
- 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
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 2 are common, 0 are distinctive, and 5 are very specific to this project.
2
Common
Most of the 3 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 63
Read current surface: readSurface(runtimeConfigDir) → if null, seed from readActiveProfile(runtimeConfigDir).
- Common: line 82
Read or initialize surface state.
- Very specific: line 83
Add cluster to surfaceState.disabledClusters (deduplicate).
- Common: line 96
Read surface state; if null, nothing to enable — print "No surface delta active."
- Very specific: line 97
Remove cluster from surfaceState.disabledClusters.
- Very specific: line 110
Check if .gsd-surface.json exists.
- Very specific: line 140
All paths can be overridden by reading the CLAUDE_CONFIG_DIR env var if set.
“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.
Files
<objective>
Manage the runtime skill surface without reinstall. Reads/writes `/home/tony/.config/opencode/.gsd-surface.json`
(sibling to `/home/tony/.config/opencode/.gsd-profile`) and re-stages the active skills directory in place.
Skill dirs live at `/home/tony/.config/opencode/skills/gsd-*/`.Sub-commands: list · status · profile · disable · enable · reset
</objective>
Sub-command routing
Parse the first token of $ARGUMENTS:
| Token | Action |
list | Show enabled + disabled clusters and skills |
status | Alias for list plus token cost summary |
profile <name> | Write baseProfile and re-stage |
profile <n1>,<n2> | Composed profiles (comma-separated, no spaces) |
disable <cluster> | Add cluster to disabledClusters, re-stage |
enable <cluster> | Remove cluster from disabledClusters, re-stage |
reset | Delete .gsd-surface.json, return to install-time profile |
| (none) | Treat as list |
list / status
Load the capability registry and call listSurface(runtimeConfigDir, manifest, CLUSTERS, registry) from
the engine module at ${runtimeConfigDir}/gsd-core/bin/lib/surface.cjs. The registry is loaded via:
const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs');Display:
Enabled (N skills, ~T tokens):
core_loop: new-project discuss-phase plan-phase execute-phase help update
audit_review: …
…
Disabled:
utility: health stats settings …
Token cost: ~T (budget cap ~500 tokens for 200k context @ 1%)For status also append:
Base profile: standard (from .gsd-surface.json)
Install profile: standard (from .gsd-profile)profile <name>
- Read current surface:
readSurface(runtimeConfigDir)→ if null, seed fromreadActiveProfile(runtimeConfigDir). - Set
surfaceState.baseProfile = name. writeSurface(runtimeConfigDir, surfaceState).- Resolve and re-apply:
const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry); - Confirm: "Surface updated to profile
<name>. N skills enabled."
disable <cluster>
Valid cluster names: core_loop, audit_review, milestone, research_ideate,
workspace_state, docs, ui, ai_eval, ns_meta, utility.
- Validate cluster name against
Object.keys(CLUSTERS). - Read or initialize surface state.
- Add cluster to
surfaceState.disabledClusters(deduplicate). writeSurface→ resolve layout →applySurface:const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry);- Confirm: "Disabled cluster
<cluster>. N skills removed from surface."
enable <cluster>
- Read surface state; if null, nothing to enable — print "No surface delta active."
- Remove cluster from
surfaceState.disabledClusters. writeSurface→ resolve layout →applySurface:const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry);- Confirm: "Enabled cluster
<cluster>. N skills added back to surface."
reset
- Check if
.gsd-surface.jsonexists. - Delete it.
- Re-apply using only
readActiveProfile(runtimeConfigDir)(install-time profile). - Confirm: "Surface reset to install-time profile
<name>."
runtimeConfigDir resolution
The runtimeConfigDir for applySurface is the base the agent config directory
(~/.config/opencode), NOT the skills sub-directory (/home/tony/.config/opencode/skills).
This matches installRuntimeArtifacts and uninstallRuntimeArtifacts, which also
receive ~/.config/opencode as configDir. The skill dirs themselves live at
/home/tony/.config/opencode/skills/gsd-*/ because the claude global layout has destSubpath =
'skills' — they are derived from configDir, not the root for it.
# Claude Code — global install
RUNTIME_CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.config/opencode}"
SCOPE="global"
# Artifact destinations are derived from runtime layout
# via resolveRuntimeArtifactLayout(runtime, RUNTIME_CONFIG_DIR, SCOPE)
# then applySurface(RUNTIME_CONFIG_DIR, layout, manifest, CLUSTERS)Surface state is stored at ${RUNTIME_CONFIG_DIR}/.gsd-surface.json
(i.e. /home/tony/.config/opencode/.gsd-surface.json).
All paths can be overridden by reading the CLAUDE_CONFIG_DIR env var if set.
Error handling
- Unknown cluster name → list valid cluster names, exit without writing.
- Unknown profile name → list known profiles (
core,standard,full), exit. - Missing
surface.cjs→ prompt: "Runnpm i -g @opengsd/gsd-coreto reinstall GSD."
<execution_context>
Surface state file: /home/tony/.config/opencode/.gsd-surface.json
Install profile marker: /home/tony/.config/opencode/.gsd-profile
Skill dirs: /home/tony/.config/opencode/skills/gsd-*/
Engine module: /home/tony/.config/opencode/gsd-core/bin/lib/surface.cjs
Cluster definitions: /home/tony/.config/opencode/gsd-core/bin/lib/clusters.cjs
</execution_context>
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.

