Solana's official Agent Skill: 48.8K installs, current docs, one big context caveat (2026)

The short verdict

Install solana-dev if your agent regularly touches Solana code and you want current ecosystem guidance in the session instead of a pile of stale project rules. The skill covers client SDKs, wallet UI, Anchor and Pinocchio programs, IDL generation, Surfpool and local testing, security checks, version compatibility, and troubleshooting. 1

The adoption signal is unusually strong for a single skill: the official skills directory lists 48.8K installs for solana-dev. The repository page currently shows 543 stars and 124 forks. 2 1 Its latest visible commit is dated July 24, 2026 and updates the wallet React hooks for kit-plugin-wallet 0.14. 3

That does not make it a finished, independently reviewed product. I could not verify a reliable seven-day star delta from the public pages, and the public issue history contains unresolved requests about context size and documentation links. My recommendation is to install it project-locally, run a small dApp task, and inspect what the agent actually cites before making it a default for every repository.

What it actually adds

This is one broad skill, not a menu of separate Solana specialists. Its SKILL.md points the agent to reference files for the parts of the stack it needs, following the Agent Skills progressive-disclosure pattern. The documented defaults are opinionated and current enough to be useful, but they are also the first things to verify against your project's lockfiles.

Area	Guidance encoded by the skill
Client SDK	`@solana/kit` v7 with plugin clients; web3.js v3 RC is treated as the migration path for older v1 codebases
Wallet and UI	Wallet Standard through `@solana/kit-plugin-wallet` and `@solana/react`
Programs	Anchor 1.1.x by default, with Pinocchio 0.11+ for performance-focused native programs
Testing	LiteSVM or Mollusk for unit tests, Surfpool for integration tests and mainnet-state workflows
Code generation	Codama-first IDL and client generation
Operations	Compatibility matrices, common-error mappings, security guidance, and one-shot RPC lookups

These choices come from the repository's README, which also lists current references for confidential transfers, payments, Anchor migration, and Surfpool cheatcodes. 1

The useful distinction is between a general Solana explainer and a project-aware coding aid. It should help an agent choose the right reference when the request is about a wallet flow, an Anchor migration, a Surfpool test, or a version mismatch. It cannot make an unsafe transaction safe, and it cannot replace checking the versions in your own repository.

Install it without global sprawl

For the shortest path, use the skills CLI:

npx skills add solana-foundation/solana-dev-skill

The repository documents that command as the cross-agent install path, and the skills directory identifies the installed item as solana-dev. The CLI route needs a working Node.js/npm environment because it runs through npx. 1 2

If you want the repository under version control, use the included Bash installer instead:

git clone https://github.com/solana-foundation/solana-dev-skill
cd solana-dev-skill
./install.sh --project

--project writes the skill into .agents/skills/solana-dev and .claude/skills/solana-dev in the current project. The default ./install.sh form installs user-level copies under ~/.agents/skills and ~/.claude/skills. Add --link if you want those locations to point at the cloned directory, so a later git pull updates the installed copy. The installer also supports --path PATH for a custom directory. 4

For a team repository, I would start with --project, commit the installation decision, and keep the skill version aligned with the codebase's Solana, Anchor, and package-manager versions. The project-local choice makes it easier to review changes and remove the skill without changing every agent on a developer's machine.

Three prompts to test the fit

The repository's own examples cover the main cases. Try these in a disposable branch rather than starting with a production wallet or deployment flow. 1

1. Build a wallet flow

Help me set up a Next.js app with Solana wallet connection.

Use the current project dependencies first. State whether you are choosing
@solana/kit, which wallet plugin and React packages you need, and which
versions you found in package.json before editing. Add a small connection test
and explain how I can verify the signing flow without sending a real transfer.

This tests whether the skill's Kit and wallet references produce a coherent plan instead of mixing an older web3.js API into a new client.

2. Create and review a program

Create an Anchor program for a simple escrow.

Before writing code, list the account constraints, signer checks, and failure
cases. Then implement the smallest version, add tests, and review the result
against Solana security guidance. Tell me which assumptions are specific to
Anchor 1.1.x and which would change in Pinocchio.

The point is to see whether the agent names its security assumptions and test boundary. Do not accept a generated program because it compiles; read the account validation and authority logic yourself.

3. Exercise the test and troubleshooting references

Write Surfpool integration tests for my token transfer flow.

First inspect the existing test runner and package versions. Explain how the
local network is started, what state is forked or created, and how the test
proves the expected token balances. If a dependency mismatch appears, stop and
show the exact version conflict before changing package files.

A shorter diagnostic test is to ask: I'm getting GLIBC_2.39 not found when running anchor. The README includes version mismatches and GLIBC errors among the intended activation cases. 1

What users are saying, and what they are not

The public feedback is useful but not yet a review consensus. In open issue #43, Taylor123 argues that the single broad skill wastes tokens and can increase context drift. The request proposes separate skills for security analysis, Anchor, Pinocchio, client development, IDL generation, testing, and payments. That is a specific criticism of the packaging, not a claim that the technical references are wrong. 5

Open issue #18 reports that the link to Solana security best practices was broken or that the Solana documentation had moved. The issue page still shows the report as open. For a security-oriented skill, that is a practical maintenance warning: an agent can only follow the reference that is actually reachable. 6

I did not find an independent rating, a published benchmark, or a substantial body of user testimonials tied to this specific skill in the sources available for this issue. The 48.8K install count shows reach, not correctness. Treat the two issue reports as field feedback, keep the caveat visible, and do not read the star count as a security review.

Where I would draw the line

Install it when:

Your agent is writing or reviewing Solana clients, programs, wallet UI, or tests.
You want one cross-agent starting point for Claude Code, Codex, Copilot, Gemini CLI, Cursor, Windsurf, Cline, and OpenCode.
You are willing to reconcile its opinionated defaults with the versions already pinned in your repository.

Sandbox or skip it when:

Your context budget is tight and you only need one narrow concern, such as Anchor testing.
You need a fully audited source of security advice rather than a maintained collection of Markdown references.
The agent can access production keys, signing wallets, deployment credentials, or live RPC write paths. Keep those privileges outside the first experiment.

The repository is MIT-licensed. Its visible activity is current, but its lack of a clean weekly star-growth measure and its open documentation and packaging issues make a small project-local trial the sensible default. 1

Quick reference

Repository	solana-foundation/solana-dev-skill
Skill name	`solana-dev`
Adoption signal	48.8K installs listed by skills.sh; 543 GitHub stars and 124 forks visible on the repository page. 2 1
Latest visible repository activity	July 24, 2026: wallet React hook documentation update. 3
License	MIT. 1
Install	`npx skills add solana-foundation/solana-dev-skill` or clone and run `./install.sh --project`
Best first task	A small wallet connection, Anchor program, or Surfpool test in a disposable branch

Install it project-locally, run one of the three prompts, and ask the agent to name the references and versions it used. Keep the skill if that makes the next review easier to audit; remove it if the broad context produces more version mixing than useful guidance.

Solana's official Agent Skill: 48.8K installs, current docs, one big context caveat