Standards logo

Standards

Organization
stellar
standards

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

Overview

Publisherstellar
Repositorystellar-dev-skill
Skill namestandards
Stars
56
Forks
64
Bundled files
2
LicenseApache-2.0
Links
  • 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.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by stellar on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/stellar/stellar-dev-skill/tree/main/skills/standards
  4. 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.
2

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/stellar/stellar-dev-skill.git /tmp/stellar-dev-skill
mkdir -p .claude/skills
cp -r /tmp/stellar-dev-skill/skills/standards .claude/skills/standards
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Standards 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 Standards 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 Standards 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.

Standards, Ecosystem, and Resources

Three things bundled because they're all reference material you reach for in the same moment: "which standard handles X?", "is there an existing project doing Y?", and "where's the canonical doc for Z?".

This file carries the SEP/CAP standards routing map. The other two live alongside it — read the file that matches the task:

TaskFile
Pick the right SEP/CAP, check standard status, map a use case to standards docsthis file
Find DeFi protocols, wallets, dev tools, indexers, oracles, bridges, builder teams, funding programsecosystem.md
Locate official docs, SDKs, CLI tools, testing guides, RPC providers, learning resources, community linksresources.md

When to use this skill

  • Picking the right SEP for an integration (anchors, deposits, federation, deep links, KYC, paths)
  • Checking CAP status for a protocol feature you want to rely on
  • Finding existing DeFi protocols, wallets, or infrastructure to integrate with rather than rebuild
  • Locating official docs, SDKs, or community resources

Related skills

  • Implementing a SEP-41 token interface → ../assets/SKILL.md, ../smart-contracts/SKILL.md
  • Frontend SEP-7 / SEP-10 flows → ../dapp/SKILL.md
  • CAPs for cryptography (BLS, BN254, Poseidon) → ../zk-proofs/SKILL.md
  • x402/MPP protocol context → ../agentic-payments/SKILL.md
  • SEP-55 verified builds for mainnet contracts → ../smart-contracts/SKILL.md

SEP / CAP Standards Reference

When to use this guide

Use this when you need:

  • The right SEP/CAP for a feature or integration
  • Interoperability guidance for wallets, anchors, and contracts
  • A fast map from use case to official standards docs

Maintenance note

Standards status can change quickly. Before implementation, verify current status in:

Treat this file as a routing map, not a source of final governance/status truth.

High-value SEPs for app developers

Contracts and token interfaces

  • SEP-0041: Soroban token interface
  • SEP-0046: Contract metadata in Wasm
  • SEP-0048: Contract interface specification
  • SEP-0049: Upgradeable-contract guidance
  • SEP-0050: NFT standard work
  • SEP-0055: Contract build verification
  • SEP-0056: Vault-style tokenized products
  • SEP-0057: Regulated token patterns (T-REX)
  • SEP-0008: Regulated classic assets (per-transaction issuer approval server)

Auth, identity, and metadata

Anchor and fiat integration

High-value CAPs for smart contract developers

Smart contract foundations

  • CAP-0046: Soroban overview
  • CAP-0046 subdocuments (cap-0046-*.md): runtime, lifecycle, host functions, storage, auth, metering

Frequently used contract capabilities

  • CAP-0051: secp256r1 verification (passkey-related cryptography)
  • CAP-0053: TTL extension behavior
  • CAP-0058: constructors (__constructor)
  • CAP-0059: BLS12-381 primitives
  • CAP-0067: protocol/runtime improvements including asset/event model changes

Newer and draft crypto/features

  • CAP-0074: BN254 host functions (G1 add/mul, pairing check) — Final, Protocol 25+
  • CAP-0075: Poseidon/Poseidon2 permutation primitives — Final, Protocol 25+
  • CAP-0079: muxed-address strkey conversion proposal
  • CAP-0080: BN254 G1 MSM, Fr arithmetic, on-curve checks — Implemented, Protocol 26+

Use the CAP preamble status fields as the source of truth for implementation readiness.

Quick mapping by use case

I am building a fungible token

  1. Start with SEP-0041 interface expectations.
  2. Prefer Stellar Assets + SAC interop unless custom logic is required.
  3. If regulated: a classic asset that needs issuer approval per transaction uses SEP-0008 (approval server); a contract token uses SEP-0057 (T-REX, Draft) patterns.

I need upgrade-safe contracts

  1. Read SEP-0049 guidance for upgrade process design.
  2. Use CAP-0058 constructors for atomic initialization where protocol support exists.
  3. Add migration/versioning strategy before deploying upgradeable contracts.

I am building a smart-wallet flow

  1. Use SEP-0010 for web authentication flows.
  2. Review CAP-0051 for passkey-related cryptographic primitives.
  3. Align wallet UX and signing payloads with current SDK guidance.

I need anchor integration for fiat rails

  1. SEP-0006 for API-first flows.
  2. SEP-0024 for hosted interactive rails.
  3. SEP-0031 when supporting payment corridors.
  4. SEP-0012 for KYC data requirements.

Practical workflow for AI agents

  • Step 1: Identify feature category (token, wallet auth, anchor, upgradeability).
  • Step 2: Link user to the 1-3 primary SEP/CAP docs.
  • Step 3: Check status/acceptance in the source repo before asserting support.
  • Step 4: Implement only what is active on the target network/protocol.
  • Step 5: Document dependencies on draft standards explicitly.

Related docs

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Standards AI skill do?

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

Why use Standards on TypingMind?

Because you install it once and use it with any model. Standards is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Standards in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/stellar/stellar-dev-skill/tree/main/skills/standards. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Standards?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Standards?

As many as you like. As long as a model supports skills, you can use Standards with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Standards AI skill free?

Yes. It is published on GitHub by stellar under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇