Add Caatinga skill to community ecosystem cards - #89
Conversation
Adds the Caatinga skill (Soroban deployment orchestration CLI, `ctg`) to ECOSYSTEM_CARDS so it appears on skills.stellar.org and in the generated llms.txt. Co-authored-by: Nearx-Labs <nearxlabs@nearx.com.br>
There was a problem hiding this comment.
Pull request overview
Adds Caatinga to the community skill catalog.
Changes:
- Adds Caatinga’s description and source link.
- Includes it in the website and generated
llms.txt.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Thanks for this, Dione — this is exactly the kind of gap I wanted the ecosystem section to fill (deployment orchestration on top of the raw Stellar CLI, not another wallet or explorer skill), and the SKILL.md itself is unusually careful. I checked the 3.9.2 "Versioning note" claim against the actual CLI changelog: the One thing I want cleared up before this goes on the catalog: the SKILL.md's "Versioning note" section says Caatinga is "pre-1.0 (alpha)," but the main repo's README says the opposite — "v1.0 stable contract on npm major Once that's fixed I'm happy to merge — everything else here checked out clean. |
Summary
ECOSYSTEM_CARDSso it appears on skills.stellar.org and in generatedllms.txt.@caatinga/cli(ctgcommand)Why this skill is useful
The catalog's
smart-contractsskill covers writing and deploying Soroban contracts with the Stellar CLI directly, but doesn't address the deployment-orchestration layer teams need once a project has multiple interdependent contracts and generated frontend bindings to keep in sync.Caatinga fills that gap for the
ctgworkflow:dependsOnincaatinga.config.ts; Caatinga topologically sorts and deploys them in the correct order instead of requiring manual sequencing.caatinga.artifacts.jsontracks contract IDs per network, replacing manual.envcopy/paste that drifts on redeploy.ctg generatekeeps frontend clients in sync with what's actually deployed.--sourceand from hand-editing generated artifacts/bindings, both common failure modes when an agent falls back to rawstellarCLI commands in a Caatinga-managed repo.This gives agents working in
ctg-based repos (signaled bycaatinga.config.ts/caatinga.artifacts.json/CAATINGA_*env vars) opinionated, project-aware guidance instead of generic Stellar CLI advice that would bypass Caatinga's invariants.Test plan
node --experimental-strip-types scripts/generate-llms-txt.mjssucceeds and the generatedllms.txtincludes the new ecosystem cardDione-b/caatinga-skilldocuments thectgworkflow, hard rules, and install steps/plugin marketplace add Dione-b/caatinga-skilland try a Caatinga-related prompt