AF solo-deploy
Deploy project to hosting platform — read stack YAML for exact config, detect local CLI tools (vercel, wrangler, supabase, fly, sst), set up database, push code, verify live deployment. Use when user says "deploy it", "push to production", "set up hosting", or after /build completes. Do NOT use before build is complete.
As a process F 48/100 · Will not run — References files that are not bundled: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md, templates/stacks/*.yaml
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- 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
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Grep Bash Glob Write Edit mcp__solograph__session_search mcp__solograph__project_code_search mcp__solograph__codegraph_query
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: templates/stacks/{stack}.yaml - warning
missing-refreference to a missing file: templates/principles/dev-principles.md - warning
missing-refreference to a missing file: templates/stacks/*.yaml
Process rating: all ten parameters 48/100
- 0Tools and files. 3 referenced file(s) missing: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md, templates/stacks/*.yaml
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 72 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Steps. 54 steps
- 100Failures and branches. 11 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3451 tokens
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 321: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.