Svm

Organization

sendaifun

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.

Overview

Publisher	sendaifun
Repository	`skills`
Skill name	`svm`
Stars	128
Forks	81
Bundled files	10
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
10 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by sendaifun on GitHub. Read the source before you install it.

Installation

Install the Svm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/sendaifun/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/svm .claude/skills/svm

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Svm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Svm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Svm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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