npx skills add davepoon/buildwithclaude --skill remove-workspace --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<context> **Arguments:** - `<workspace-name>` (required) — Name of the workspace to remove </context> <objective> Remove a workspace directory after confirmation. For worktree strategy, runs `git worktree remove` for each member repo first. Refuses if any repo has uncommitted changes. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/remove-workspace.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md </execution_context> <process> Execute the remove-workspace workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/remove-workspace.md end-to-end. </process>
What does the gsd:remove-workspace skill do?
Remove a GSD workspace and clean up worktrees
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill remove-workspace --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.