BC gsd
Get Shit Done - Full project planning and execution workflow. Handles project initialization with deep context gathering, automated research, roadmap creation, phase planning, and execution with verification.
Get Shit Done - Full project planning and execution workflow.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-background-processreferences/ccr-integration.md:178Starts a background / autostarted processnohup bash .planning/autopilot.sh > .planning/logs/autopilot.log 2>&1 &
-
low Broad scope
meta-dynamic-shelltemplates/discovery.md:22Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`date +%Y-%m-%d`
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 18 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 96 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2178 tokens
- low The response is described with custom markup (9 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 208: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 96 items
- +4Reference files are cited in the instructions (2 of 15)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.