gsd-surface

Enable, disable, and switch runtime skill profiles for Claude Code.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-surface-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-surface
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-surface
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-surface-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of quickly changing which Claude skills and clusters are active at runtime without going through a reinstall or regenerating the whole setup.

Core Features & Use Cases

  • Runtime surface management: Lists enabled/disabled clusters and skills, including an approximate token cost view for the active surface.
  • Profile-based reconfiguration: Applies a base profile (or composed profiles) by updating the surface state and re-staging the active commands/gsd directory in place.
  • Cluster toggling: Disables or re-enables specific clusters (e.g., core_loop, utility, docs) to tailor behavior for different tasks or budgets.
  • Use Case: When you want faster, lower-token operation for a focused workflow, disable higher-cost clusters and switch to a smaller runtime profile; when you need broader coverage, re-enable the clusters and restore the original profile.

Quick Start

Run gsd-surface profile standard to re-stage the active commands/gsd surface to the standard base profile.

Frequently Asked Questions about gsd-surface

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch active Claude Code skills at runtime without reinstalling?

You can switch active Claude Code skills at runtime by using a surface management profile to re-stage the active commands directory in place, avoiding a full environment reinstall or reset.

What is runtime skill surface management for Claude Code?

Runtime skill surface management controls which skill clusters are staged for Claude Code by reading and writing a configuration file to enable, disable, and switch profiles on the fly.

Can I reduce token costs by disabling specific Claude Code skill clusters?

Yes, you can reduce token costs by disabling higher-cost skill clusters and switching to a smaller runtime profile for focused workflows, then re-enabling them when broader coverage is needed.

How do I apply a base profile to re-stage the active commands directory?

To apply a base profile and re-stage the active commands directory, execute the surface staging logic with your resolved profile name to update the runtime skill state instantly.

Does managing the skill surface require resetting the whole Claude environment?

No, managing the skill surface does not require resetting the whole environment because it validates cluster inputs and re-applies changes by updating the surface state in place.

What are the limitations of using profiles to manage the runtime skill surface?

A limitation of using profiles to manage the runtime skill surface is that it relies on a specific configuration file path and depends on executing the staging logic from the underlying get-shit-done framework.