open-gsd/gsd-core

gsd-surface

Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall

First seen Jun 23, 2026

Installation

$ npx skills add open-gsd/gsd-core --skill gsd-surface

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from open-gsd/gsd-core · top by installs.

npx skills add open-gsd/gsd-core

Browse all from open-gsd/gsd-core

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9.3K
License LICENSE
Default branch next
Open issues 129
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Bash
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,052 B
  • docs SUMMARY.md 114 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 254 installs

SKILL.md

<objective> Manage the runtime skill surface without reinstall. Reads/writes ~/.claude/.gsd-surface.json (sibling to ~/.claude/.gsd-profile) and re-stages the active skills directory in place. Skill dirs live at ~/.claude/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)

Mutation protocol

Derive the next surfaceState in memory and pass it to applySurface as opts.surfaceState. Do not call writeSurface first: applySurface stages all artifact kinds before mutation and publishes the candidate state only after materialization succeeds. Pass null to reset to the install-time profile.


profile \<name\>

  1. Read current surface: readSurface(runtimeConfigDir) → if null, seed from readActiveProfile(runtimeConfigDir).
  2. Set surfaceState.baseProfile = name.
  3. Keep the new state in memory; do not write it directly.
  4. Resolve and re-apply:

``js const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry, { surfaceState }); ``

  1. Confirm: "Surface updated to profile <name>. N skills enabled."

disable \<cluster\>

Valid cluster names: coreloop, auditreview, milestone, researchideate, workspacestate, docs, ui, aieval, nsmeta, utility.

  1. Validate cluster name against Object.keys(CLUSTERS).
  2. Read or initialize surface state.
  3. Add cluster to surfaceState.disabledClusters (deduplicate).
  4. Resolve layout and apply the in-memory candidate:

``js const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry, { surfaceState }); ``

  1. Confirm: "Disabled cluster <cluster>. N skills removed from surface."

enable \<cluster\>

  1. Read surface state; if null, nothing to enable — print "No surface delta active."
  2. Remove cluster from surfaceState.disabledClusters.
  3. Resolve layout and apply the in-memory candidate:

``js const registry = require(runtimeConfigDir + '/gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry, { surfaceState }); ``

  1. Confirm: "Enabled cluster <cluster>. N skills added back to surface."

reset

  1. Check if .gsd-surface.json exists.
  2. Do not delete it directly.
  3. Re-apply with { surfaceState: null }; the state file is removed only after

the install-time profile materializes successfully.

  1. Confirm: "Surface reset to install-time profile <name>."

runtimeConfigDir resolution

The runtimeConfigDir for applySurface is the base Claude config directory (~/.claude), NOT the skills sub-directory (~/.claude/skills).

This matches installRuntimeArtifacts and uninstallRuntimeArtifacts, which also receive ~/.claude as configDir. The skill dirs themselves live at ~/.claude/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/.claude}"
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 ${RUNTIMECONFIGDIR}/.gsd-surface.json (i.e. ~/.claude/.gsd-surface.json).

All paths can be overridden by reading the CLAUDECONFIGDIR 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: "Run npm i -g @opengsd/gsd-core to reinstall GSD."

<executioncontext> Surface state file: ~/.claude/.gsd-surface.json Install profile marker: ~/.claude/.gsd-profile Skill dirs: ~/.claude/skills/gsd-*/ Engine module: ~/.claude/gsd-core/bin/lib/surface.cjs Cluster definitions: ~/.claude/gsd-core/bin/lib/clusters.cjs </executioncontext>