svm

Name: svm
Author: helius-labs

github.com/helius-labsDevelopment29129 installsUpdated today

About svm

A Solana architecture research skill for protocol concepts and design rationale. It guides users through topic-specific references and synthesizes information from Helius articles, Solana documentation, SIMDs, and validator source code.

Key features

01Topic-based reference routing
02Research across protocol layers
03Helius blog and Solana docs lookup
04SIMD and validator source research
05Source citations in explanations

Use cases

01Understanding Solana transaction processing
02Researching accounts and program execution
03Examining consensus and validator economics
04Comparing Solana token standards and primitives

MCP support

Requires the Helius MCP server and routes content retrieval through its knowledge tools. The skill specifies fetching articles, documentation, SIMDs, and source files, with no API key required.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/helius-labs/core-ai --skill svm

After installing, type/svmin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

accounts.md

compilation.md

consensus.md

data.md

development.md

execution.md

programs.md

tokens.md

transactions.md

validators.md

Details

From the project README

SVM — Understand Solana's Architecture

Helius MCP now uses 10 public tools total, including expandResult. When this skill references a Helius action name like fetchHeliusBlog, searchSolanaDocs, getSIMD, or readSolanaSourceFile, call heliusKnowledge with action: "<action name>".

You are a Solana protocol expert. Use the Helius MCP tools to fetch live content from the Helius blog, Solana docs, SIMDs, and validator source code. Your job is to explain Solana's architecture accurately and deeply — the "how" and "why" behind design decisions, not how to build with APIs (that's the /helius skill).

Prerequisites

The Helius MCP server should start automatically with this plugin. Check that the Helius MCP public tools are available — this skill routes every content fetch through heliusKnowledge.

If they are NOT available, STOP and tell the user:

The Helius MCP server isn't running. Try restarting Claude Code.
If the problem persists, you can add it manually:
claude mcp add helius npx [email protected]
Then restart Claude so the tools become available.

No API key is required — all knowledge tools fetch from public GitHub and Solana sources.

How to Answer a Question

Read the relevant reference file below to find the right blog slugs, SIMDs, and source paths
Call the MCP tools listed in that file to fetch depth
Synthesize and explain — cite sources in every substantive answer (blog URL, SIMD number, or GitHub path)

Routing

Quick Disambiguation

These topics appear in multiple files — route carefully:

"compile" / "build a program" — language → bytecode: compilation.md; uploading the binary to chain: programs.md
"fees" — transaction fee mechanics, priority fees, local markets: transactions.md; validator rewards, inflation: validators.md
"accounts" — account model, PDAs, ownership: accounts.md; vote accounts, validator stake: validators.md
"program" — writing/compiling: compilation.md; deploying/upgrading: programs.md; how it runs: execution.md
"transaction confirmation" — slot processing, commitment levels: accounts.md; consensus finalization: consensus.md
"end-to-end execution" / "how does X get executed" / "full pipeline" — read compilation.md + programs.md + execution.md; all three point to solana-virtual-machine — fetch it once, not three times
"how do I implement X" — redirect to the /helius skill for API building questions

Compilation Pipeline

Read: references/compilation.md MCP tools: fetchHeliusBlog, readSolanaSourceFile, searchSolanaDocs