# Stellar Development Skill
A comprehensive AI skill for modern Stellar development with current best practices. https://skills.stellar.org/
Inspired by [solana-foundation/solana-dev-skill](https://github.com/solana-foundation/solana-dev-skill) and [cloudflare/skills](https://github.com/cloudflare/skills).
> [!NOTE]
> This skill was AI-generated using [Claude Code](https://claude.ai/code) and is currently under manual review. We welcome contributions! Please submit PRs, open issues, or provide feedback to help improve this resource for the Stellar ecosystem.
## Overview
This skill provides AI assistants with deep knowledge of the current Stellar development ecosystem:
- **Smart Contracts**: Stellar smart contracts (Rust soroban-sdk, WebAssembly)
- **Client SDKs**: stellar-sdk (JavaScript), Python, Go, Rust
- **APIs**: Stellar RPC (preferred), Horizon (legacy)
- **Assets**: Stellar Assets, Stellar Asset Contract (SAC)
- **Wallets**: Varial, Stellar Wallets Kit, Smart Accounts (passkeys)
- **Testing**: Local Quickstart, Testnet, Unit tests
- **Security**: Smart contract security patterns, audit checklists
- **Ecosystem**: DeFi protocols, developer tools, community projects
## Raven: live MCP server
These skills give your agent durable Stellar context, baked in. [Raven](https://raven.stellar.buzz) is a complementary **remote Model Context Protocol (MCP) server** for on-demand lookups: connect an agent and it searches Stellar docs and live ecosystem data, cross-referenced into single answers. Its catalog also includes these skills, so Raven is a live delivery gateway for them. Use both: skills for durable best practices, Raven for current lookups.
Raven is open source at [kalepail/stellar-raven](https://github.com/kalepail/stellar-raven). Connect it in Claude Code:
```bash
claude mcp add --transport http stellar-raven "https://raven.stellar.buzz/mcp"
```
You can also try Raven in the browser at the [playground](https://raven.stellar.buzz/playground), a hosted chat UI for asking Raven questions (sign-in required).
## Stellar Docs MCP: official docs server
The [Stellar Docs MCP server](https://developers.stellar.org/docs/build/building-with-ai#stellar-docs-mcp-server) searches and reads the official Stellar docs, including the OpenAPI specs. It needs no sign-in and also serves these skills as MCP resources. Use it when you want answers from the docs only. Use Raven when you also need live ecosystem data.
```bash
claude mcp add --transport http --scope user stellar-docs "https://developers.stellar.org/mcp"
```
## Installing
These skills work with any agent that supports the [Agent Skills](https://agentskills.io) standard.
### [Claude Code](https://code.claude.com/docs/en/discover-plugins#add-from-github)
```bash
# Add this repo as a marketplace
/plugin marketplace add stellar/stellar-dev-skill
# Then install the skill
/plugin install stellar-dev@stellar-dev
```
### [OpenAI Codex](https://learn.chatgpt.com/docs/build-skills)
```bash
git clone https://github.com/stellar/stellar-dev-skill ~/.agents/skills/stellar-dev-skill
```
Codex still reads the older `~/.codex/skills/` path, but that path is deprecated.
### [npx skills](https://skills.sh)
```bash
npx skills add https://github.com/stellar/stellar-dev-skill
```
### [OpenClaw](https://docs.openclaw.ai/tools/skills)
Copy all skills into OpenClaw's shared skills directory, which every local agent can see:
```bash
git clone https://github.com/stellar/stellar-dev-skill
mkdir -p ~/.openclaw/skills && cp -R stellar-dev-skill/skills/* ~/.openclaw/skills/
```
### Clone / Copy
```bash
git clone https://github.com/stellar/stellar-dev-skill
```
Copy the `skills/` directory contents to your assistant's skills location.
| Agent | Skill Directory | Docs |
|-------|-----------------|------|
| Claude Code | `~/.claude/skills/` | [docs](https://code.claude.com/docs/en/skills) |
| OpenCode | `~/.config/opencode/skill/` | [docs](https://opencode.ai/docs/skills/) |
| OpenAI Codex | `~/.agents/skills/` | [docs](https://learn.chatgpt.com/docs/build-skills) |
| OpenClaw | `~/.openclaw/skills/` | [docs](https://docs.openclaw.ai/tools/skills) |
| Pi | `~/.pi/agent/skills/` | [docs](https://github.com/badlogic/pi-mono/tree/main/packages/coding-agent#skills) |
## Skill Structure
```
skills/
├── smart-contracts/ # Stellar smart contracts — SKILL.md router + development/testing/security files
├── dapp/ # Frontend — SKILL.md router + react / data-fetching / smart-accounts files
├── assets/SKILL.md # Stellar Assets, trustlines, SAC bridge
├── data/ # Stellar RPC (preferred) — SKILL.md router + horizon (legacy) file
├── agentic-payments/ # AI/machine payments — SKILL.md router + x402 / mpp files
├── zk-proofs/SKILL.md # ZK verification (BLS12-381/BN254 Groth16, UltraHonk), Circom/Noir/RISC Zero
├── standards/ # SEPs & CAPs — SKILL.md router + ecosystem / resources files
└── cross-chain/ # Cross-chain — SKILL.md router + cctp / axelar / layerzero files
```
Each sub-skill is a self-contained Agent Skill with its own frontmatter. Larger skills follow [Anthropic's progressive-disclosure guidance](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices): a sub-500-line `SKILL.md` router with a task-to-file table, plus companion files (one level deep) that load only when the task needs them. Cross-references link related skills (e.g., the `agentic-payments` skill points to `smart-contracts` for the SACs the protocols call, and to `assets` for USDC). The AI reads only the files relevant to the task at hand.
## Example Prompts
```
"Help me write a Stellar smart contract for a token"
"Set up a Next.js app with Varial wallet connection"
"How do I deploy a contract to Stellar Testnet?"
"Create unit tests for my smart contract"
"Review this contract for security issues"
```
## Contributing
Contributions are welcome! Please ensure any updates reflect current Stellar ecosystem best practices.
1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Submit a pull request
### Guidelines
- Keep information current (check stellar.org/developers for updates)
- Focus on practical, actionable guidance
- Include code examples where helpful
- Cite official documentation when possible
- Keep each `SKILL.md` body under ~500 lines — move deep dives into companion files routed by the task table
- When a change touches what a skill teaches, update or add the matching scenario under [`evals/`](evals/README.md) in the same PR
## Evaluations
[`evals/`](evals/README.md) holds ~3 task scenarios for each of the eight skills (plus cross-skill routing checks and a negative control), each encoding a mistake agents actually make without the skill. Three grading tiers: machine-checkable compile checks, LLM-judged behavior assertions, and skill-trigger checks. One gap is open: no baseline transcripts are committed, so the set is still unvalidated. See [evals/README.md](evals/README.md) for the format, how to run them, and what the missing baselines mean.
## Resources
- [Stellar Developers](https://developers.stellar.org)
- [Stellar Discord](https://discord.gg/stellardev)
- [Stellar Stack Exchange](https://stellar.stackexchange.com)
- [SDF Blog](https://stellar.org/blog)
## License
Apache-2.0 License - see [LICENSE](LICENSE) for details.
---
> **Note:** This repository is not in scope for the Stellar Development Foundation bug bounty program. Vulnerabilities found in this repo are not eligible for rewards.