BF solana-dev
End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.
End-to-end Solana development playbook (Jan 2026).
As a process F 34/100 · Will not run — References files that are not bundled: frontend-framework-kit.md, kit-web3-interop.md, programs-anchor.md
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 · 0
✓ No critical or high findings
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: frontend-framework-kit.md - warning
missing-refreference to a missing file: kit-web3-interop.md - warning
missing-refreference to a missing file: programs-anchor.md - warning
missing-refreference to a missing file: programs-pinocchio.md - warning
missing-refreference to a missing file: testing.md - warning
missing-refreference to a missing file: idl-codegen.md - warning
missing-refreference to a missing file: payments.md - warning
missing-refreference to a missing file: security.md - warning
missing-refreference to a missing file: resources.md
Process rating: all ten parameters 34/100
- 0Tools and files. 9 referenced file(s) missing: frontend-framework-kit.md, kit-web3-interop.md, programs-anchor.md
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (solana-dev) differs from the folder (solana-trade)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 52 steps
- 100Execution cost. Instruction body is 869 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 518: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 52 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.