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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

60%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 content is highly actionable with concrete commands and a thorough finding template, but it is let down by broken references to a missing VULNERABILITY_PATTERNS.md, an empty Example Output section, and some redundancy. Fixing the missing reference file would substantially improve progressive disclosure.

Suggestions

Create the referenced resources/VULNERABILITY_PATTERNS.md file (or remove the broken links) so the signaled navigation target actually resolves.

Fill or delete the empty §5 "Example Output" section to avoid a dangling heading.

Collapse the duplicated vulnerability listing between §6 Pattern Summary and §9 Priority Guidelines to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with actionable rg commands and code, but it has redundant restatements (the pattern summary in §6 vs. priorities in §9, and the VULNERABILITY_PATTERNS.md link repeated) and an empty §5 "Example Output" section that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready rg commands, checklists, and a complete finding template with vulnerable and fixed Rust code, but the unit-test bodies in §10 are stubs ("// Provide wrong program ID, should fail") rather than executable tests, leaving a minor gap.	4 / 5
Workflow Clarity	A clear six-step scanning workflow with per-step checklists and a final §12 checklist sequences the work well; because scanning is read-only the destructive-operation cap does not apply, though explicit validate-then-proceed feedback loops are mostly implicit rather than spelled out.	4 / 5
Progressive Disclosure	The body repeatedly signals [VULNERABILITY_PATTERNS.md](resources/VULNERABILITY_PATTERNS.md) for detail, but no resources/ directory or that file exists, so the navigation target is broken; combined with the empty §5 "Example Output" section, the disclosure structure fails to resolve.	2 / 5
	Total	13 / 20 Passed

Description

92%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, third-person description that concretely names the capability and its trigger conditions with a clear niche. Minor improvement possible by adding common synonyms or file markers, but it answers what and when explicitly.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates multiple concrete vulnerability classes ("arbitrary CPI, improper PDA validation, missing signer/ownership checks, and sysvar spoofing"), giving comprehensive coverage of what is scanned.	5 / 5
Completeness	It explicitly states both what it does ("Scans Solana programs for 6 critical vulnerabilities including...") and when to use it ("Use when auditing Solana/Anchor programs") with a concrete trigger clause.	5 / 5
Trigger Term Quality	Natural terms like "auditing Solana/Anchor programs" and "Scans Solana programs" appear, but it lacks common synonyms or file/extension markers, so a few natural phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The Solana/Anchor security-auditing niche is distinct with specialized triggers (CPI, PDA, sysvar), making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: d1f1575

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.