← Products

Blockchain
⚙ Needs: a Stellar integration question (which SEP applies, w…

Stellar standards map — SEPs, CAPs and ecosystem references

Pick the right Stellar standard — SEP/CAP routing map for wallets, anchors, payments and tokens, plus ecosystem and docs references

At a glance
What
Pick the right Stellar standard — SEP/CAP routing map for wallets, anchors, payments and tokens, plus ecosystem and docs references
Cost
Free
Needs
a Stellar integration question (which SEP applies, which standard to implement) — the skill is reference guidance, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @stellar
⌁

Install

Prerequisites: a Stellar integration question (which SEP applies, which standard to implement) — the skill is reference guidance, not software Install "Stellar standards map — SEPs, CAPs and ecosystem references" for me. It gives my agent Stellar's official standards routing map: which SEP/CAP applies to what (SEP-41 token interface, SEP-7/SEP-10 frontend flows, anchors, federation, KYC, deposits and withdrawals), bundled ecosystem references (DeFi protocols, wallets, dev tools, indexers, bridges, funding programs), curated docs links and live MCP tooling references such as Raven. The skill itself warns that standards status changes fast — verify current status against the official repos before implementing. Apache-2.0 licensed. Repository: https://github.com/stellar/stellar-dev-skill/blob/main/skills/standards/SKILL.md 1. Fetch the SKILL.md file (and any helper files, including ecosystem.md and resources.md) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "standards". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent which SEP or ecosystem question to answer; nothing else — it's a reference map). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.