Skip to content

Add Caatinga skill to community ecosystem cards - #89

Open
Dione-b wants to merge 3 commits into
stellar:mainfrom
Nearx-Labs:feat/add-caatinga-skill
Open

Add Caatinga skill to community ecosystem cards#89
Dione-b wants to merge 3 commits into
stellar:mainfrom
Nearx-Labs:feat/add-caatinga-skill

Conversation

@Dione-b

@Dione-b Dione-b commented Aug 13, 2026

Copy link
Copy Markdown

Summary

Why this skill is useful

The catalog's smart-contracts skill 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 ctg workflow:

  • Deployment Graph — contracts declare dependsOn in caatinga.config.ts; Caatinga topologically sorts and deploys them in the correct order instead of requiring manual sequencing.
  • Versioned artifacts as source of truthcaatinga.artifacts.json tracks contract IDs per network, replacing manual .env copy/paste that drifts on redeploy.
  • Generated TypeScript bindingsctg generate keeps frontend clients in sync with what's actually deployed.
  • Credential hygiene — the skill actively steers agents away from passing raw secret keys via --source and from hand-editing generated artifacts/bindings, both common failure modes when an agent falls back to raw stellar CLI commands in a Caatinga-managed repo.

This gives agents working in ctg-based repos (signaled by caatinga.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.mjs succeeds and the generated llms.txt includes the new ecosystem card
  • Skill on Dione-b/caatinga-skill documents the ctg workflow, hard rules, and install steps
  • Confirm card renders under Community skills on the preview deploy
  • Optional: install the plugin via /plugin marketplace add Dione-b/caatinga-skill and try a Caatinga-related prompt

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>
Copilot AI balanced review requested due to automatic review settings August 13, 2026 03:06

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread site/src/data/skills.ts Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment thread site/src/data/skills.ts Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@kaankacar

Copy link
Copy Markdown
Contributor

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 os.tmpdir() key-leak fix and the ctg sync-env env-file-wipe fix you cite are both real, 3.9.2 is genuinely npm's current latest, and the wallet-adapter / single-invoker claims match docs/wallets.md in the main caatinga repo too.

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 3.x" — and npm's latest is 3.9.2, well past a 1.0 line. That's a real contradiction an agent reading the skill could act on (e.g. telling someone not to trust it in production when the project itself calls it stable). Could you update or drop that line in skills/caatinga/SKILL.md so it doesn't contradict the project's own README?

Once that's fixed I'm happy to merge — everything else here checked out clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants