Stellar Dev Skill: building on Stellar
Stellar Development Skill
Eight Stellar Development Foundation skills: Rust contracts, SDKs, RPC, assets, wallets and security reviews
- 59 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skill is instructions only and runs nothing itself
- Code for the main network touches real money, so a human reviews the agent's output before deployment
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/stellar-development-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill is instructions only and runs nothing itself
- Code for the main network touches real money, so a human reviews the agent's output before deployment
This is third-party code. Review the repository files before installing.
What it does
The skills give an agent a working picture of the Stellar ecosystem. One covers smart contracts in Rust with soroban-sdk, another a React client with the Freighter wallet and passkey smart accounts, a third data queries through Stellar RPC and the legacy Horizon. Others handle asset issuance and the Stellar Asset Contract, payments between agents over x402 and MPP, zero-knowledge proof verification and transfers between networks through CCTP, Axelar and LayerZero. Each skill is a router: a SKILL.md under 500 lines with a task-to-file table. For a contract the agent opens development, testing or security separately and keeps the rest out of context. The evals folder holds check scenarios: several per skill, routing checks and a control example unrelated to Stellar. The authors say the material was generated with Claude Code and is under manual review.
Who it is for. Teams writing Stellar smart contracts in Rust, wallets and payments who want the agent to know current network practice.
Good fit when
- A Rust contract fails on authorization, storage or resource-limit errors and you need a pointer to the cause
- A new token needs issuance through the Stellar Asset Contract with trustlines
- A React front end must connect Freighter and call a contract
- Before a contract audit you want to walk through a checklist of vulnerability classes
- Requests between agents must be paid for over x402 or MPP
Not a fit when
- The project is entirely on Solana or Ethereum with no bridge to Stellar
- You need current prices, rates or market state: the skill holds practice, while live documentation lookups come from the separate Raven server
- You need a security verdict on a contract: the skill's checklists do not replace an auditor
- The task is a single stellar-cli command whose answer is quicker to find in the documentation
Example request
Write a SEP-41 token contract in Rust, add tests and walk it through the security checklist.Limitations
The material was generated with Claude Code and is under manual review, so check code and security advice against the Stellar documentation. Examples target protocol 29, soroban-sdk 29 and stellar-cli 28, and the version numbers in them are illustrative: take current ones from crates.io and Stellar Lab. The skill does not search documentation or the ecosystem live, and the authors point to the Raven server for that. The repository is outside the Stellar bug bounty program. No baseline transcripts of the check scenarios are recorded yet.
How to disable. In Claude Code remove the plugin with `/plugin uninstall stellar-dev@stellar-dev`. For other agents delete the skill folder from the skills directory.
FAQ
How do I install Stellar Dev Skill in Claude Code?
Run `/plugin marketplace add stellar/stellar-dev-skill`, then `/plugin install stellar-dev@stellar-dev`. For other agents use `npx skills add https://github.com/stellar/stellar-dev-skill`.
How do the skills differ from the Raven server?
The skills keep durable practice in the agent's context, while Raven is a remote MCP server for live lookups in the documentation and ecosystem data. The authors suggest installing both. Connect the server with `claude mcp add --transport http stellar-raven "https://raven.stellar.buzz/mcp"`.
Why do the skills say both Soroban and Stellar?
The smart contract platform used to be branded Soroban. The name is retired, but the Rust SDK soroban-sdk and several tools kept the prefix. The smart-contracts skill also answers requests that say Soroban.
Which skill covers the front end?
The dapp skill: React, data fetching and smart accounts. The agent loads it from its description when the task involves the Freighter wallet or calling a contract from the browser.
Which agents does it work with?
Any agent that supports the Agent Skills standard. The repository lists paths for Claude Code, Codex, OpenClaw, OpenCode and Pi: copy the contents of the `skills/` directory into the agent's skills folder.
Discussion
No questions or reviews yet.
Related
SkillsA Solana Foundation skill for Solana development: Anchor and Pinocchio, @solana/kit clients, wallets, Surfpool and LiteSVM testing, security
Skills for building and upgrading smart contracts on OpenZeppelin libraries in Solidity, Cairo, Stylus, Stellar and Sui
Over 200 skills by stack and practice: React, Next.js, Rails, Rust, Python, debugging, TDD and UI review
A set of skills from real work: npm supply-chain audit, CLI building, Obsidian plugin release and an AGENTS.md hierarchy
Corrections to what AI agents know about Ethereum: current gas, contract addresses, L2s, standards and smart contract security
Nine skills for building on Chainlink: CRE, CCIP, Data Feeds, Data Streams, VRF and other network products
README in short
The set was inspired by the Solana Foundation and Cloudflare skills. The repository holds eight skills, a Claude Code plugin manifest, evaluation scenarios and install routes for Claude Code, Codex, OpenClaw, OpenCode and Pi. The remote Raven server complements the skills.
README badge
Original SKILL.md
--- name: smart-contracts description: Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code. user-invocable: true argument-hint: "[contract task]" --- # Stellar Smart Contracts Guide for building Stellar smart contracts in Rust. Smart contracts on Stellar were formerly branded "Soroban" — the platform name is retired, but the Rust SDK (`soroban-sdk`) and several tool names keep the prefix. This file covers setup and the core workflow. The deep dives live alongside it — **read the file that matches the task**: | Task | File | |------|------| | Storage/TTL, authorization, constructors, cross-contract calls, tokens, events, errors, upgrades, factories, governance/DeFi patterns, fees/resources, troubleshooting | [development.md](development.md) | | Unit, integration, fuzz, property, fork, and mutation testing | [testing.md](testing.md) | | Security review, vulnerability classes, checklists, audit prep, tooling | [security.md](security.md) | ## When to use this skill - Writing a Stellar smart contract in Rust - Setting up contract tests (any layer) - Reviewing a contract for security issues - Architecting upgradeable contracts, factories, custom accounts, or DeFi primitives - Debugging a contract-specific error (auth, storage, archival, resource limits) ## Related skills - Asset issuance, trustlines, and SAC deployment → `../assets/SKILL.md` - Frontend/wallets that call your contract → `../dapp/SKILL.md` - Chain data queries (RPC/Horizon) → `../data/SKILL.md` - ZK verification (BLS12-381, Groth16, Circom/Noir/RISC Zero) → `../zk-proofs/SKILL.md` - SEP/CAP standards and ecosystem links → `../standards/SKILL.md` ## Versions This skill was written against **protocol 29** (`soroban-sdk` v29, `rs-soroban-env` v29, `stellar-cli` v28). Version numbers in examples are illustrative — resolve the current ones from these sources rather than trusting any doc: - **`soroban-sdk` major version tracks the protocol version** (SDK 29 ↔ protocol 29). This rule outlives any specific release. - **Build with `stellar contract build`** (`stellar-cli` v25.2.0+). From `soroban-sdk` 28, a plain `cargo build` for a Wasm target stops with an error, because the CLI must strip unreachable spec entries after compiling. Native `cargo test` is unaffected. - Latest SDK release: [crates.io/crates/soroban-sdk](https://crates.io/crates/soroban-sdk) (or `cargo add soroban-sdk`, which resolves it). Pre-releases (`-rc.x`) exist only during a protocol rollout and must be pinned with the exact version string; [GitHub releases](https://github.com/stellar/rs-soroban-sdk/releases) lists them with changelogs. - Networks upgrade by validator vote, testnet before mainnet — pin the SDK major matching the network you deploy to. Live protocol version: RPC `getVersionInfo` or [Stellar Lab](https://lab.stellar.org). - Numeric network limits quoted here are mainnet settings at time of writing; they change by vote — [Stellar Lab's Network Limits page](https://lab.stellar.org/network-limits) and `stellar network settings --network mainnet` show the live values. ## Platform constraints