near-api-js Developer Guide
internet-court/internet-court-skill
Reference for building with near-api-js v7 in TypeScript or JavaScript: accounts, keys, signing, contract calls, tokens, unit conversion and meta-transactions on NEAR.
End-to-end Stellar development playbook. An agent skill from VelaPayments/vela-payments.
Install Stellar Dev
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VelaPayments/vela-payments stellar-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stellar-dev .claude/skills/stellar-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .claude/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VelaPayments/vela-payments stellar-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/stellar-dev .agents/skills/stellar-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .agents/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VelaPayments/vela-payments stellar-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/stellar-dev .cursor/skills/stellar-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .cursor/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/VelaPayments/vela-payments.git --path .agents/skills/stellar-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VelaPayments/vela-payments stellar-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/stellar-dev .gemini/skills/stellar-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .gemini/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install VelaPayments/vela-payments stellar-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/stellar-dev .github/skills/stellar-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .github/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VelaPayments/vela-payments --skill stellar-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VelaPayments/vela-payments stellar-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VelaPayments/vela-payments.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/stellar-dev .opencode/skills/stellar-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stellar-dev" agent skill from https://github.com/VelaPayments/vela-payments/tree/main/.agents/skills/stellar-dev into .opencode/skills/stellar-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stellar-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
stellar-dev- GitHub stars
- 131
- Token cost
- ~1.8k tokens
- SKILL.md length
- 646 words
- Files
- 13
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
End-to-end Stellar development playbook. An agent skill from VelaPayments/vela-payments.
- Works in 12 steps: Smart Contracts: Soroban (Rust) → Client SDK: stellar-sdk (JavaScript) first → API Access: Stellar RPC first (Horizon… → …
- Building on Stellar
- SKILL.md covers What this Skill is for, What this Skill is NOT for, Default stack decisions… and Operating procedure (how to…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stellar Dev is an agent skill from VelaPayments/vela-payments. End-to-end Stellar development playbook. Covers Soroban smart contracts (Rust SDK), Stellar CLI, JavaScript/Python/Go SDKs for client apps, Stellar RPC (preferred) and Horizon API (legacy), Stellar Assets vs Soroban tokens (SAC bridge), wallet integration (Freighter, Stellar Wallets Kit), smart accounts with passkeys, status-sensitive zero-knowledge proof patterns, testing strategies, security patterns, and common pitfalls. Optimized for payments, asset tokenization, DeFi, privacy-aware applications, and…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `advanced-patterns.md`, `api-rpc-horizon.md` and `common-pitfalls.md`).
It sits in Backend & APIs, covering Smart contract auditing, Smart contracts and Cryptography. It works with Stellar, Rust, JavaScript and Python. The repository describes itself as: Open-source mobile payment prototype on Stellar, featuring NFC payment requests, XLM and USDC wallets, and passkey access. The licence is MIT.
When your agent uses it
- Building on Stellar
- Working with XLM
- The Stellar RPC/Horizon APIs
Example prompts
- “/stellar-dev”
Requirements
- Node.js
- Docker
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- Smart Contracts: Soroban (Rust)
- Client SDK: stellar-sdk (JavaScript) first
- API Access: Stellar RPC first (Horizon legacy-focused)
- Token Strategy: Stellar Assets first
- Testing
- Wallet Integration
- Freshness policy
- Classify the task layer
- Pick the right building blocks
- Implement with Stellar-specific correctness
- Add tests
- Deliverables expectations
What it can do on your machine
Read from SKILL.md and the folder at commit 25ff9b0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.stellar.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Stellar Dev loads about 1.8k tokens when it runs. Until then it costs about 173 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from VelaPayments/vela-payments at commit 25ff9b0, republished under its MIT licence (© VelaPayments). 646 words, ~1,752 tokens.
Download SKILL.mdSave it as
.claude/skills/stellar-dev/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- stellar-dev
- description
- End-to-end Stellar development playbook. Covers Soroban smart contracts (Rust SDK), Stellar CLI, JavaScript/Python/Go SDKs for client apps, Stellar RPC (preferred) and Horizon API (legacy), Stellar Assets vs Soroban tokens (SAC bridge), wallet integration (Freighter, Stellar Wallets Kit), smart accounts with passkeys, status-sensitive zero-knowledge proof patterns, testing strategies, security patterns, and common pitfalls. Optimized for payments, asset tokenization, DeFi, privacy-aware applications, and financial applications. Use when building on Stellar, Soroban, or working with XLM, Stellar Assets, trustlines, anchors, SEPs, ZK proofs, or the Stellar RPC/Horizon APIs.
- user-invocable
- true
- argument-hint
- [task-description]
Stellar Development Skill (Soroban-first)
What this Skill is for
Use this Skill when the user asks for:
- Soroban smart contract development (Rust)
- Stellar dApp frontend work (React / Next.js / Node.js)
- Wallet connection + signing flows (Freighter, etc.)
- Transaction building / sending / confirmation
- Stellar Asset issuance and management
- Client SDK usage (JavaScript, Python, Go, Rust)
- Zero-knowledge proof verification (where supported by target network/protocol)
- Privacy-preserving applications (privacy pools, confidential tokens)
- Local testing and deployment
- Security hardening and audit-style reviews
What this Skill is NOT for
- Bitcoin, Ethereum, Solana, or other non-Stellar blockchain development
- Stellar node/validator operation (see validators docs)
- General Rust programming unrelated to Soroban
- Stellar protocol governance or CAP authoring
Default stack decisions (opinionated)
1. Smart Contracts: Soroban (Rust)
- Use Soroban SDK (
soroban-sdkcrate) for all smart contract development - Contracts compile to WebAssembly (WASM)
- Use
#![no_std]- standard library not available - 64KB contract size limit - use release optimizations
- Prefer Stellar Assets over custom token contracts when possible
2. Client SDK: stellar-sdk (JavaScript) first
- Use
@stellar/stellar-sdkfor browser and Node.js applications - Supports both Stellar RPC and legacy Horizon API
- Full transaction building, signing, and submission
- Soroban contract deployment and invocation
3. API Access: Stellar RPC first (Horizon legacy-focused)
- Prefer Stellar RPC for new projects (JSON-RPC, real-time state)
- Horizon API remains available for legacy compatibility and historical-query workflows
- RPC: 7-day history for most methods;
getLedgersqueries back to genesis (Infinite Scroll) - Use Hubble/Galexie for comprehensive historical data beyond RPC
4. Token Strategy: Stellar Assets first
- Prefer Stellar Assets (classic issuance + trustlines) for fungible tokens
- Built-in ecosystem support (wallets, exchanges, anchors)
- Stellar Asset Contracts (SAC) provide Soroban interoperability
- Use custom Soroban tokens only for complex logic requirements
5. Testing
- Local: Use Stellar Quickstart Docker for local network
- Testnet: Use Testnet with Friendbot for funding
- Unit tests: Compile to native for fast iteration
- Integration tests: Deploy to local/testnet
6. Wallet Integration
- Freighter is the primary browser wallet
- Use Stellar Wallets Kit for multi-wallet support
- Wallet Standard for consistent connection patterns
7. Freshness policy
- Verify volatile facts (protocol support, RPC endpoints, CAP/SEP status, SDK API changes) against official docs before asserting them as current.
Operating procedure (how to execute tasks)
1. Classify the task layer
- Smart contract layer (Soroban/Rust)
- Client SDK/scripts layer (JS/Python/Go)
- Frontend/wallet layer
- Asset management layer (issuance, trustlines)
- Testing/CI layer
- Infrastructure (RPC/Horizon/indexing)
Show full SKILL.md (272 more words)Show less
Quick routing
- Need custom on-chain logic? → contracts-soroban.md
- Building a frontend/dApp? → frontend-stellar-sdk.md
- Issuing or managing tokens? → stellar-assets.md
- Zero-knowledge proofs or privacy? → zk-proofs.md
- Setting up tests/CI? → testing.md
- Querying chain data or indexing? → api-rpc-horizon.md (also see Data Docs)
- Security review? → security.md
- Hit an error? → common-pitfalls.md
- Need upgrade/factory/governance/DeFi architecture patterns? → advanced-patterns.md
- Need SEP/CAP guidance and standards links? → standards-reference.md
2. Pick the right building blocks
- Contracts: Soroban Rust SDK + Stellar CLI
- Frontend: stellar-sdk (JS) + Freighter/Wallets Kit
- Backend: stellar-sdk (JS/Python/Go) + RPC
- Assets: Classic operations or SAC for Soroban interop
- Testing: Quickstart (local) or Testnet
3. Implement with Stellar-specific correctness
Always be explicit about:
- Network passphrase (Mainnet vs Testnet vs local)
- Source account + sequence number
- Fee + resource limits (for Soroban)
- Authorization requirements
- Trustline status for assets
- Contract storage types (temporary vs persistent vs instance)
4. Add tests
- Unit tests: Native compilation with
#[test] - Integration tests: Local Quickstart or Testnet
- Contract tests: Use
Envfrom soroban-sdk - Frontend tests: Mock wallet/RPC interactions
5. Deliverables expectations
When you implement changes, provide:
- Exact files changed + diffs
- Commands to install/build/test/deploy
- Network configuration (passphrase, RPC endpoint)
- Risk notes for signing/fees/storage/authorization
Progressive disclosure (read when needed)
- Smart contracts: contracts-soroban.md
- Frontend + wallets: frontend-stellar-sdk.md
- Testing strategy: testing.md
- Stellar Assets: stellar-assets.md
- Zero-knowledge proofs: zk-proofs.md
- API access (RPC/Horizon): api-rpc-horizon.md
- Security checklist: security.md
- Common pitfalls: common-pitfalls.md
- Advanced architecture patterns: advanced-patterns.md
- SEP/CAP standards map: standards-reference.md
- Ecosystem projects: ecosystem.md
- Reference links: resources.md
Keywords
stellar, soroban, xlm, smart contracts, rust, wasm, webassembly, rpc, horizon, freighter, stellar-sdk, soroban-sdk, stellar-cli, trustline, anchor, sep, passkey, smart wallet, sac, stellar asset contract, defi, token, nft, scaffold stellar, constructor, upgrade, factory, governance, standards, zero-knowledge, zk, zk-snark, groth16, bn254, poseidon, pairing, privacy, confidential, noir, risc zero, privacy pool, merkle tree
© VelaPayments, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 12 other files in .agents/skills/stellar-dev of VelaPayments/vela-payments.
- SKILL.md
- advanced-patterns.md
- api-rpc-horizon.md
- common-pitfalls.md
- contracts-soroban.md
- ecosystem.md
- frontend-stellar-sdk.md
- resources.md
- security.md
- standards-reference.md
- stellar-assets.md
- testing.md
- zk-proofs.md
Open the folder on GitHubat commit 25ff9b0
Used in 1 other repository
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in VelaPayments/vela-payments, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Stellar Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stellar Dev this skillVelaPayments/vela-payments | 131 | — | ~1.8k | Automated safety check: Pass | MIT | |
| near-api-js Developer Guideinternet-court/internet-court-skill | 6.4k | 1 repos | ~4.1k | Automated safety check: Pass | Custom licence | |
| Constant-Time Analysistrailofbits/skills | 7.4k | — | ~3.3k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Security Reviewgithub/awesome-copilot | 40k | 1 repos | ~2.3k | Automated safety check: Notes | MIT | |
| Solidity Vulnerability Scanneralt-research2/SolidityGuard | 104 | — | ~1.6k | Automated safety check: Notes | Custom licence | |
| Stellar iOS Mac SDKSoneso/stellar-ios-mac-sdk | 132 | — | ~4.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Constant-Time Analysis
trailofbits/skills
Compiles cryptographic code and inspects the assembly or bytecode for variable-time instructions, then triages which flagged operations actually touch secrets.
- Official
Security Review
github/awesome-copilot
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching…
Solidity Vulnerability Scanner
alt-research2/SolidityGuard
Comprehensive Solidity contract security scanner detecting 104 vulnerability patterns across reentrancy, access control, arithmetic, DeFi, proxy, and token categories.
Stellar iOS Mac SDK
Soneso/stellar-ios-mac-sdk
Guides Stellar blockchain development in Swift using stellar-ios-mac-sdk.
deBridge Solana SDK Guide
internet-court/internet-court-skill
Guides building Solana programs with the deBridge SDK for cross-chain token transfers, message passing and external calls to EVM chains.
Related
Works with
Categories
Questions about Stellar Dev
What does Stellar Dev do?
End-to-end Stellar development playbook. An agent skill from VelaPayments/vela-payments. Stellar Dev is an agent skill from VelaPayments/vela-payments. End-to-end Stellar development playbook.
When should I use Stellar Dev?
Stellar Dev fits situations like: building on Stellar; working with XLM; the Stellar RPC/Horizon APIs.
How do I install Stellar Dev in Claude Code?
Run `npx skills add VelaPayments/vela-payments --skill stellar-dev -a claude-code`. Or copy the skill folder (.agents/skills/stellar-dev in VelaPayments/vela-payments) into .claude/skills/stellar-dev in your project. Claude Code loads it when a task matches its description.
How do I install Stellar Dev in Codex?
Run `npx skills add VelaPayments/vela-payments --skill stellar-dev -a codex`. Or copy the skill folder (.agents/skills/stellar-dev in VelaPayments/vela-payments) into .agents/skills/stellar-dev in your project. Codex loads it when a task matches its description.
Can I use Stellar Dev in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VelaPayments/vela-payments --skill stellar-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stellar-dev, .gemini/skills/stellar-dev, .github/skills/stellar-dev and .opencode/skills/stellar-dev in your project.
What does Stellar Dev need to run?
SKILL.md names no scripts, command-line tools or credentials: Stellar Dev is instructions for the agent only. Our summary lists: Node.js; Docker.
Does Stellar Dev access the network?
SKILL.md names 1 domain. As links in the text: developers.stellar.org. This is read from the text; nothing was executed.
Is Stellar Dev safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Stellar Dev use?
Stellar Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Stellar Dev use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Stellar Dev?
Skills that share tags, products or a category with Stellar Dev: near-api-js Developer Guide (internet-court/internet-court-skill, 6.4k stars), Constant-Time Analysis (trailofbits/skills, 7.4k stars), Security Review (github/awesome-copilot, 40k stars) and Solidity Vulnerability Scanner (alt-research2/SolidityGuard, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stellar Dev?
VelaPayments (a GitHub organization) maintains it in VelaPayments/vela-payments, which has 131 GitHub stars. The repository was last updated on October 6, 2026.
Source: VelaPayments/vela-payments on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.