CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

solana-vulnerability-scanner

Scans Solana programs for 6 critical vulnerabilities including arbitrary CPI, improper PDA validation, missing signer/ownership checks, and sysvar spoofing. Use when auditing Solana/Anchor programs.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/building-secure-contracts/skills/solana-vulnerability-scanner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The scanning workflow itself is excellent — sequenced, command-driven, and enforced by an explicit coverage-table validation gate and anti-rationalization section. However, its core detection detail is delegated to a file missing from the bundle, and roughly a third of the body (empty §5, stub tests, the duplicate §12 checklist) is padding that undercuts token efficiency.

Suggestions

Ship resources/VULNERABILITY_PATTERNS.md (or inline the six detection patterns into §6): the body points to it twice for the skill's core detection logic, but the file is absent from the bundle, leaving §6 a bare summary.

Cut the ~100 lines of duplication and dead weight: delete the empty §5 'Example Output', merge the §12 quick-reference checklist into the §7 per-step checklists it repeats, and either make the §10 test bodies executable or drop them.

Fix Step 6: the Trail of Bits lint configuration is a commented placeholder ('# Enable Solana-specific lints'); give the actual Cargo.toml lints configuration or remove the step, and either reference or delete the unused assets/trail-of-bits-mark.svg.

DimensionReasoningScore

Conciseness

The scanning steps and §8/§13 are dense and earn their tokens, but §5 'Example Output' is an empty header, §12 (~40 lines) restates the §7 checklists and §6 patterns, §10 is ~60 lines of stub tests, and §6 points to VULNERABILITY_PATTERNS.md twice within twelve lines. Mostly efficient with several sections that could be tightened — matching the 3 anchor rather than 2, since no space is spent teaching concepts Claude already knows.

3 / 5

Actionability

Steps 2–5 supply copy-paste `rg` commands with per-item checklists, and the finding template with its Anchor fix is complete. But the actual detection patterns — the skill's core detail — are deferred to resources/VULNERABILITY_PATTERNS.md, which is absent from the bundle, the §10 test bodies are non-executable stubs ('// Provide wrong program ID, should fail'), and Step 6's lint configuration is a placeholder comment. Concrete guidance with material incompleteness, matching the 3 anchor rather than 4, where gaps would be minor.

3 / 5

Workflow Clarity

Six clearly sequenced steps each carry checkbox criteria, and §8's coverage table is an explicit validation gate ('A table with fewer than 6 rows is an incomplete scan and must be reported as one') with per-verdict rules, reinforced by §13's rationalizations to reject — matching the 5 anchor's explicit validation steps and process checklists.

5 / 5

Progressive Disclosure

The one reference is clearly signaled and one level deep, but resources/VULNERABILITY_PATTERNS.md does not exist in the bundle (only assets/trail-of-bits-mark.svg, itself never referenced), so navigation to the detailed patterns the skill depends on fails outright, while ~130 lines of template and testing content that belongs in the referenced file are inlined in SKILL.md. This matches the 2 anchor — structure that should be split is inlined and the reference is effectively dead — rather than 3, where references would be present and usable but poorly organized.

2 / 5

Total

13

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete about what it scans for, with an explicit 'Use when' trigger clause. Its only weaknesses are the partial enumeration of the 6 vulnerability classes and a single, somewhat narrow trigger phrase.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('arbitrary CPI, improper PDA validation, missing signer/ownership checks, and sysvar spoofing') in third person, but 'including' names only 4 of the 6 claimed vulnerability classes, leaving minor coverage gaps that fall short of the comprehensive anchor.

4 / 5

Completeness

Both parts are present and explicit — the 'what' ('Scans Solana programs for 6 critical vulnerabilities including...') and the 'when' ('Use when auditing Solana/Anchor programs'). It falls short of the 5 anchor because the single trigger phrase is narrower than the multi-phrase concrete triggers in the anchor example, and short of nothing below because the 'when' is explicit, not implied.

4 / 5

Trigger Term Quality

'auditing Solana/Anchor programs', 'CPI', 'PDA', and 'sysvar' are natural terms for this audience, matching the good-keyword-coverage anchor; common variations like 'security review', 'audit', or 'smart contract' are missing.

4 / 5

Distinctiveness Conflict Risk

Solana/Anchor program auditing is a sharp niche with distinct, unambiguous triggers ('Solana', 'Anchor', 'CPI', 'PDA', 'sysvar spoofing'); minimal conflict risk with any other skill.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

trailofbits/skills

Path

plugins/building-secure-contracts/skills/solana-vulnerability-scanner/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.