CC golive
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email…
As a process C 67/100 · Has gaps — References files that are not bundled: references/<provider>.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-pipe-to-shell-known-hostreferences/godaddy.md:16Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)`curl -fsSL https://github.com/godaddy/cli/releases/latest/download/install.sh | bash` — and the
quoted
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 12583 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/<provider>.md
Process rating: all ten parameters 67/100
- 0Tools and files. 1 referenced file(s) missing: references/<provider>.md
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 12583 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 49 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (11 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
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 669: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (7 of 16)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.