helius-tech-labshelius-tech-labs/core-ai/.agents/skills/svm/SKILL.md

svm

Skill0 starsChanged 8 months agoMITView on GitHub

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 the Helius skill skill). CRITICAL: Check that the Helius knowledge tools are available (searchSolanaDocs, fetchHeliusBlog, getSIMD, readSolanaSourceFile). If they are NOT available, STOP and tell the user: No…

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

helius-labs/core-aiedited, first seen Nov 3, 2026
muralidharsoth-tech/andrew-ng-ml-claude-skillstheir own version, first seen Oct 15, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
helius-labs/core-ai★ 3090% same
Wrote their own version · 1
muralidharsoth-tech/andrew-ng-ml-claude-skills★ 40same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- helius-cli/CLAUDE.mdCLAUDE.md
- helius-mcp/CLAUDE.mdCLAUDE.md
- helius-dflowSkill
- helius-okxSkill
- helius-phantomSkill
- heliusSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
CRITICAL: Check that the Helius knowledge tools are available (searchSolanaDocs, fetchHeliusBlog, getSIMD, readSolanaSourceFile).
line 22
Distinctive:
No API key is required — all knowledge tools fetch from public GitHub and Solana sources.
line 30
Distinctive:
Read the relevant reference file below to find the right blog slugs, SIMDs, and source paths
line 34
Distinctive:
Call the MCP tools listed in that file to fetch depth
line 35
Distinctive:
Use this when the user asks about:
line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

name: svm version: "1.0.0" description: > Explore Solana's architecture and protocol internals. Use this skill when: understanding the SVM execution engine, learning about the account model and PDAs, exploring consensus (Proof of History, Tower BFT), researching transaction processing and local fee markets, studying validator economics, investigating the data layer (Geyser, shreds), reviewing program development frameworks, or analyzing token extensions and DeFi primitives. Requires helius-mcp MCP server for knowledge tools.

SVM — Understand Solana's Architecture

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:
npx helius-mcp@latest  # configure in your MCP client
Then restart your AI assistant 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 the Helius skill skill for API building questions

Compilation Pipeline

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