svm
Explore Solana's architecture and protocol internals. Covers the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using the Helius blog, SIMDs, and Agave/Firedancer source code.
About this skill
This AI agent skill transforms an AI into a Solana protocol expert, enabling it to delve deep into Solana's core architecture and internal mechanisms. It goes beyond basic API usage to explain the "how" and "why" behind design decisions, covering critical components such as the Solana Virtual Machine (SVM), account model, consensus mechanisms, transaction processing, validator economics, data layer, development tooling, and token extensions. Users can query the agent for in-depth explanations of specific Solana concepts, request detailed breakdowns of architectural components, or ask for historical context on design choices. It's particularly useful for learning about Solana's technical foundation rather than just how to build decentralized applications (dApps). The skill provides access to authenticated, current information from reliable sources like the Helius blog, Solana documentation, Solana Improvement Documents (SIMDs), and even direct validator source code, all fetched via Helius MCP tools. This ensures accuracy and depth, making it an invaluable resource for developers, researchers, and enthusiasts looking to truly understand Solana's underlying technology.
Best use case
The primary use case for this skill is to provide comprehensive, expert-level explanations of the Solana blockchain's internal architecture and protocol design. It's ideal for developers, researchers, blockchain architects, and technical enthusiasts who need to understand the fundamental mechanisms, design decisions, and intricate workings of Solana, rather than just how to interact with its APIs. Users benefit by gaining a deep technical understanding, enabling them to make more informed decisions when building, optimizing, or analyzing Solana-based systems.
Explore Solana's architecture and protocol internals. Covers the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using the Helius blog, SIMDs, and Agave/Firedancer source code.
Users should expect accurate, detailed, and well-sourced explanations of Solana's architecture and protocol internals, citing specific blog URLs, SIMD numbers, or GitHub paths.
Practical example
Example input
Explain the Solana Virtual Machine (SVM) and how it optimizes for parallel transaction processing, citing relevant SIMDs or source code paths.
Example output
The Solana Virtual Machine (SVM) is Solana's execution engine, designed for high-throughput and parallel transaction processing, a key differentiator from traditional sequential EVMs. It compiles smart contracts (written in Rust, C, C++) into eBPF bytecode for efficient, secure execution. This architecture allows transactions targeting different state partitions to be processed concurrently. For further details, refer to [SIMD-0001: Solana Parallel Execution](https://simd.solana.com/s/SIMD-0001) and the Agave validator source code at `programs/bpf_loader/src/lib.rs`.
When to use this skill
- When you need an in-depth explanation of Solana's core architecture, like SVM or consensus.
- To understand the "how" and "why" behind Solana's design decisions and protocol internals.
- For research into Solana's validator economics, data layer, or transaction processing.
- When you need to fetch information directly from the Helius blog, SIMDs, or Solana source code.
When not to use this skill
- When you need to learn how to build applications or interact with Solana APIs (use the `/helius` skill instead).
- For simple, high-level overviews of Solana that don't require deep technical explanations.
- If you have not installed the Helius MCP server as a prerequisite.
- For questions about general blockchain concepts not specific to Solana's implementation.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/svm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How svm Compares
| Feature / Agent | svm | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | easy | N/A |
Frequently Asked Questions
What does this skill do?
Explore Solana's architecture and protocol internals. Covers the SVM execution engine, account model, consensus, transactions, validator economics, data layer, development tooling, and token extensions using the Helius blog, SIMDs, and Agave/Firedancer source code.
How difficult is it to install?
The installation complexity is rated as easy. You can find the installation instructions above.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# SVM — Understand Solana's Architecture 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 **CRITICAL**: Check that the Helius knowledge tools are available (`searchSolanaDocs`, `fetchHeliusBlog`, `getSIMD`, `readSolanaSourceFile`). If they are NOT available, **STOP** and tell the user: ``` You need to install the Helius MCP server first: claude mcp add helius npx helius-mcp@latest 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 1. Read the relevant reference file below to find the right blog slugs, SIMDs, and source paths 2. Call the MCP tools listed in that file to fetch depth 3. 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` Use this when the user asks about: - How Rust (or C/C++/Zig) programs are compiled to Solana bytecode - LLVM IR, MIR, eBPF, and sBPF — how they relate and differ - Why Solana chose eBPF as its bytecode target - The compilation toolchain and LLVM backend ### Program Deployment **Read**: `references/programs.md` **MCP tools**: `fetchHeliusBlog`, `readSolanaSourceFile`, `searchSolanaDocs` Use this when the user asks about: - How compiled programs get uploaded to the blockchain - BPF loader versions (original, V2, Upgradeable, V4) and their differences - The deploy/upgrade/close lifecycle and authority model - ELF format and the two-account program model ### Execution Engine **Read**: `references/execution.md` **MCP tools**: `fetchHeliusBlog`, `readSolanaSourceFile`, `searchSolanaDocs` Use this when the user asks about: - How sBPF bytecode is actually executed inside a validator - JIT compilation from sBPF to native machine code - Memory regions, compute units, and determinism constraints - sBPF ISA — registers, opcodes, and memory model ### Account Model & Programming Model **Read**: `references/accounts.md` **MCP tools**: `fetchHeliusBlog`, `searchSolanaDocs`, `readSolanaSourceFile` Use this when the user asks about: - How Solana's account model works (ownership, rent, data layout) - Program Derived Addresses (PDAs) — derivation, use cases, signing - Cross-Program Invocations (CPIs) — how programs call each other - Syscalls, slots, blocks, epochs, and commitment levels ### Transactions & Local Fee Markets **Read**: `references/transactions.md` **MCP tools**: `fetchHeliusBlog`, `getSIMD`, `searchSolanaDocs` Use this when the user asks about: - Transaction structure and why upfront account declarations matter - Sealevel — Solana's parallel execution model and how it differs from EVM - Local fee markets — why contention is per-account, not global - TPU pipeline, priority fees, MEV, SWQoS, blockhash, nonces - How to land transactions reliably on Solana ### Consensus **Read**: `references/consensus.md` **MCP tools**: `fetchHeliusBlog`, `getSIMD`, `readSolanaSourceFile` Use this when the user asks about: - Proof of History, Tower BFT, and how finality works - Turbine block propagation and Gulf Stream mempool forwarding - QUIC adoption and why it replaced raw UDP - Firedancer — Jump Crypto's independent validator client - Alpenglow — the next-generation consensus proposal ### Validator Economics **Read**: `references/validators.md` **MCP tools**: `fetchHeliusBlog`, `getSIMD`, `searchSolanaDocs` Use this when the user asks about: - How validators earn rewards and the economics of running one - Solana's inflation schedule and token issuance model - Slashing proposals and current safety guarantees - Decentralization metrics, governance, and the SIMD process ### Data Layer **Read**: `references/data.md` **MCP tools**: `fetchHeliusBlog`, `searchSolanaDocs`, `readSolanaSourceFile` Use this when the user asks about: - How Solana RPC nodes work and their data access patterns - Geyser plugins — streaming account and transaction data from inside a validator - Shreds — how blocks are broken into erasure-coded fragments for propagation - State compression and ZK compression ### Program Development **Read**: `references/development.md` **MCP tools**: `fetchHeliusBlog`, `searchSolanaDocs`, `readSolanaSourceFile` Use this when the user asks about: - Solana program frameworks — Anchor, Steel, Pinocchio, Gill - Optimizing programs for compute units and performance - sBPF assembly-level optimization techniques - The Solana web3.js 2.0 SDK architecture ### Token Extensions & DeFi Primitives **Read**: `references/tokens.md` **MCP tools**: `fetchHeliusBlog`, `searchSolanaDocs`, `readSolanaSourceFile` Use this when the user asks about: - Token-2022 — the new token standard and its extensions - Liquid Staking Tokens (LSTs) and how they work on Solana - Stablecoins on Solana — the landscape and mechanisms - Real World Assets (RWAs) — tokenization approaches on Solana ## Rules - **Always read the reference file first** — it lists the best slugs, SIMDs, and source paths for that topic - **Call at most 1–2 MCP tools per question** — pick the single most relevant slug from the reference file based on the specific question; don't call every slug listed - **Prefer `fetchHeliusBlog` over `searchSolanaDocs`** — blog posts are focused and authoritative; use `searchSolanaDocs` only for protocol-level concepts not covered in the blog - **Never write files** — synthesize and respond in-conversation only; do not create local markdown or text files with fetched content - **Cite sources** in every substantive answer: blog URL (`https://helius.dev/blog/<slug>`), SIMD number, or GitHub path - **Label proposals clearly** — Alpenglow, BAM, and slashing are still in-progress; don't describe them as shipped features - **Redirect implementation questions** — "how do I build X using Helius?" belongs in the `/helius` skill - **No API key needed** — `fetchHeliusBlog`, `searchSolanaDocs`, `getSIMD`, and `readSolanaSourceFile` all work without authentication
Related Skills
helius
Build Solana applications with Helius infrastructure. Covers transaction sending (Sender), asset/NFT queries (DAS API), real-time streaming (WebSockets, Laserstream), event pipelines (webhooks), priority fees, wallet analysis, and agent onboarding.
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
tavily-search
Use Tavily API for real-time web search and content extraction. Use when: user needs real-time web search results, research, or current information from the web. Requires Tavily API key.
baidu-search
Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.
agent-autonomy-kit
Stop waiting for prompts. Keep working.
Meeting Prep
Never walk into a meeting unprepared again. Your agent researches all attendees before calendar events—pulling LinkedIn profiles, recent company news, mutual connections, and conversation starters. Generates a briefing doc with talking points, icebreakers, and context so you show up informed and confident. Triggered automatically before meetings or on-demand. Configure research depth, advance timing, and output format. Walking into meetings blind is amateur hour—missed connections, generic small talk, zero leverage. Use when setting up meeting intelligence, researching specific attendees, generating pre-meeting briefs, or automating your prep workflow.
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
botlearn-healthcheck
botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.
linkedin-cli
A bird-like LinkedIn CLI for searching profiles, checking messages, and summarizing your feed using session cookies.
notebooklm
Google NotebookLM 非官方 Python API 的 OpenClaw Skill。支持内容生成(播客、视频、幻灯片、测验、思维导图等)、文档管理和研究自动化。当用户需要使用 NotebookLM 生成音频概述、视频、学习材料或管理知识库时触发。