BF solana_deploy_engineer
Sets up Solana/Anchor development environments, prepares dApps for deployment, runs build/test/deploy workflows, and guides safe devnet/mainnet release operations with verifiable builds, buffer-based upgrades, priority-fee tuning, structured failure recovery, and memory logging.
As a process F 56/100 · Will not run — References files that are not bundled: templates/env.example.template
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Broad scope
meta-agent-memory-dumpmemory/deploy-history.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokensmemory/deploy-history.md, memory/error-catalog.md, memory/project-notes.md, memory/version-decisions.md
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5341 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: templates/env.example.template
Process rating: all ten parameters 56/100
- 0Tools and files. 1 referenced file(s) missing: templates/env.example.template
- 0Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (solana_deploy_engineer) differs from the folder (solana-deploy-engineer)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5341 tokens
- 85Steps. 250 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 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 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (19 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
- +1No license
- +2Single-language instructions
- +3Description length 279: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 250 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.