CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

solana-dev

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain Solana concepts" (rent, accounts, PDAs, CPIs). Also for program architecture (state layout, compute units, throughput, naming), quick on-chain lookups via public RPC + curl, gasless or sponsored-fee transactions (Kora), server-side signing with KMS/Turnkey/Privy/Fireblocks (Solana Keychain), and issuing stablecoins or allowlisted tokens (Mosaic). Covers wallets, Anchor/Pinocchio, Codama clients, Surfpool/LiteSVM/Mollusk testing, security review, and v1 transactions (SIMD-0385). Prefers @solana/kit 8 plugin clients building transaction v1 by default, @solana/kit-plugin-wallet + @solana/react for wallets, web3.js v3 as the legacy migration target, and Surfpool for local networks.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A strong, opinionated overview that establishes defaults, safety guardrails, and an operating procedure, with an exemplary progressive-disclosure structure verified against the real bundle. The main improvement levers are removing the description-duplicating trigger list, consolidating the repeated v1-default statements, and adding a couple of inline snippets for the routing-only task paths.

Suggestions

Cut or compress the 'What this Skill is for' section — it restates the frontmatter description almost verbatim; a one-line pointer to the trigger list would save ~15 lines.

State the transaction-v1-by-default rule once (section 1) and reference it from sections 2, 3, and the operating procedure instead of re-explaining it in each place.

Add a minimal inline code example for at least one routing-only path (e.g., a 5-line Anchor program skeleton or a token-creation call) so the most common program-layer tasks have executable guidance before deferring to references/programs/anchor.md.

DimensionReasoningScore

Conciseness

The body is dense and operational (tables, short bullets, executable snippets, no explaining of concepts Claude already knows), but has trimmable redundancy: the 15-line "What this Skill is for" list largely restates the frontmatter description, and the v1-by-default rule is repeated in sections 1, 2, 3, and the operating procedure. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the level-5 'every token earns its place' anchor, and it is well above the level-3 'mostly efficient' anchor.

4 / 5

Actionability

Core paths are copy-paste ready — the `createClient().use(...)` chain with `transactionConfig: { version: 1 }`, `NO_DNA=1 anchor build/test`, MCP install commands per host, `await createClient().use(surfpool())` — plus concrete API names (`walletSigner()`, `keychainSigner()`, `airdropSigner()`) and the `maxSupportedTransactionVersion: 1` read-side flag. However, several common task types (writing an Anchor/Pinocchio program, token creation, confidential transfers) get routing-only treatment with no inline example, matching 'mostly executable guidance; concrete code or commands with minor gaps' rather than the fully-covering level-5 anchor.

4 / 5

Workflow Clarity

The five-step operating procedure (classify layer → pick blocks → implement with an explicit correctness checklist → add tests → deliverables with risk notes) is clearly sequenced, and the guardrails supply real validation checkpoints for risky operations ("Simulate before sending. Always run `simulateTransaction`", explicit approval before signing, devnet-by-default). It falls short of the level-5 anchor because error-recovery feedback loops are only implicit — failures route to common-errors.md rather than an explicit validate→fix→retry loop in the procedure itself.

4 / 5

Progressive Disclosure

The body is a genuine overview: all deep material (transactions-v1.md ~32KB, security.md ~34KB, testing.md ~21KB) lives in bundle files, and a dedicated "Progressive disclosure (read when needed)" index lists ~28 references with one-line scope descriptions. Every referenced path was verified to exist in the bundle, references are one level deep with no nested chains, and inline links are contextually placed. This matches 'clear overview with well-signaled one-level-deep references; easy navigation'.

5 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: explicit 'Use when' triggers in natural user voice, a concrete capability inventory, named tools/defaults, and a tightly bounded Solana niche. Its only weakness is length — it packs a lot of clauses into one paragraph — but every clause carries trigger or capability information rather than padding, so no dimension is penalized.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "deploy to devnet", "quick on-chain lookups via public RPC + curl", "server-side signing with KMS/Turnkey/Privy/Fireblocks", "issuing stablecoins or allowlisted tokens" — with comprehensive coverage across the dApp, program, testing, and infra layers. This matches the 'multiple specific concrete actions; comprehensive coverage' anchor; nothing is generic filler, so it does not fit the level-4 'minor gaps' anchor.

5 / 5

Completeness

It explicitly answers 'when' with an "Use when user asks to ..." clause of concrete trigger phrases and "Also for ..." extensions, and 'what' with "Covers wallets, Anchor/Pinocchio, Codama clients, Surfpool/LiteSVM/Mollusk testing, security review, and v1 transactions" plus stated defaults ("Prefers @solana/kit 8 plugin clients building transaction v1 by default"). Both what and when are explicit and concrete, matching the top anchor rather than the level-4 'when could be more explicit' anchor.

5 / 5

Trigger Term Quality

It quotes natural user phrasings users would actually say — "set up wallet connection", "test my Solana program", "fuzz my Solana program", "support larger transactions", "fix maxSupportedTransactionVersion" — plus synonyms and tool/error-level terms (dapp, Anchor, devnet, SIMD-0385, Kora, Mosaic, Token-2022). This is comprehensive natural-term coverage including variations; it clearly exceeds the 'a few natural terms missing' level-4 anchor.

5 / 5

Distinctiveness Conflict Risk

The Solana-specific niche is unambiguous — every trigger names Solana ecosystem terms (Anchor, Pinocchio, devnet, PDAs, SPL/Token-2022, Surfpool) that no other skill domain would claim, giving minimal conflict risk. It clearly fits 'clear niche with distinct triggers' rather than the level-4 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 14 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

boranfurkan/discordlancer

Path

.claude/skills/solana-dev/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.