← Search

Stellar standards map — SEPs, CAPs and ecosystem references
Blockchain 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 390fbce
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Stellar integration question (which SEP applies…

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:

Quick answer

Stellar standards map is a free Muse skill and Stellar's official standards skill, routing which SEP or CAP applies to what across wallets, anchors, payments and tokens. It covers the SEP-41 token interface, SEP-7 and SEP-10 frontend flows, anchors, federation, KYC, deposits and withdrawals, plus bundled ecosystem references, curated docs links and live MCP tooling references.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 390fbce

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/stellar/stellar-dev-skill/390fbce4ecda2c7a8d240eca42cef4d4fca487fb/skills/standards/SKILL.md Pinned version: install the code at commit 390fbce4ecda2c7a8d240eca42cef4d4fca487fb exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files, including ecosystem.md and resources.md) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 390fbce · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
390fbce · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.