Add XOXNO Lending to the ecosystem catalog and skill cards - #132
mihaieremia wants to merge 2 commits into
Conversation
- standards/ecosystem.md: XOXNO Lending entry under Lending & Borrowing (controller and swap-router entry points, docs, typed SDK and OpenAPI specs, pointer to the XOXNO agent-skill router) - site: ECOSYSTEM_CARDS entry pointing at XOXNO/rs-lending-xlm skills/xoxno-lending/SKILL.md - evals: standards scenario covering lending-protocol routing
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6647b16ebc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
Adds XOXNO Lending to Stellar ecosystem documentation, skill cards, and lending-protocol evaluation coverage.
Changes:
- Documents XOXNO’s architecture, APIs, contracts, and skill routing.
- Adds the XOXNO community skill card.
- Adds a lending-protocol routing scenario.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Summary |
|---|---|
skills/standards/ecosystem.md |
Adds XOXNO Lending documentation. Findings: qualify the generic account id trigger (moderate, 1 vote) and label network-specific contracts (nit, 1 vote). |
site/src/data/skills.ts |
Adds the XOXNO community skill card. |
evals/scenarios/standards/04-lending-protocols.json |
Adds lending-protocol routing evaluation coverage. |
Suppressed comments (2)
skills/standards/ecosystem.md:88
- This entry says XOXNO is live on both mainnet and testnet, but the controller and swap-router addresses here have no network qualifier. Unlike the K2 section's explicit
Mainnet contractslabel, this makes it easy for a testnet integrator to copy the wrong IDs; please label these values and direct readers to the network-specific entries inaddresses.md.
- **Entry point**: lending — `controller` `CAUCMIN5KSXEVZ7NMXR3LZATGD5EFIEUI5XWTFLYRO2R5OTXI22WE5JX` (not the pool). Swaps — aggregator router `CCVENFSVCBYDHVOACFZXMNNYVOZ3LKXPZYU5LUI4N7KTXOKRVYD7F3TR`. Hubs, spokes, listed markets, and every other address: [addresses.md](https://github.com/XOXNO/rs-lending-xlm/blob/main/skills/xoxno-lending/addresses.md), generated from `configs/networks.json` — re-check before hard-coding.
skills/standards/ecosystem.md:82
- The bare phrase
account idis not XOXNO-specific and appears in ordinary Stellar account/API questions, so this routing rule can make unrelated requests fetch the external lending skill. Remove this trigger or qualify it (for example,XOXNO account idor the exactaccount_ididentifier).
**Load the skill** when the task mentions XOXNO Lending, `rs-lending-xlm`, hub/spoke, `HubAssetKey`, position NFT, account id, `multiply`, `flash_position` (vs `flash_loan`), `@xoxno/sdk-js` `stellar-lending`, `api.xoxno.com/stellar-lending`, or `stellar-swap.xoxno.com`. Fetch [skills/xoxno-lending/SKILL.md](https://github.com/ghraw/XOXNO/rs-lending-xlm/main/skills/xoxno-lending/SKILL.md) and follow its routing table.
Note
Copilot is running an experiment and ran this review at Lite.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🤖 Automated message from Kaan's Automated Triage Bot. Thanks for this — the entry is unusually well sourced, and the address discipline ("re-check before hard-coding") is exactly right for a catalog entry. I verified the contract claims and they hold up. Both IDs are live on Stellar mainnet, and the deployed controller's wasm hash matches One process note: you are a member of the XOXNO org, and this adds XOXNO to the official Two content points are worth fixing while it waits. Codex and Copilot each raised them, and I confirmed both:
One item I could not settle: the three |
Drop generic "account id" and "multiply" from the catalog load instruction so an ecosystem lookup does not fetch the XOXNO skill. Label the controller and swap-router IDs as mainnet and send testnet lookups to addresses.md. Update the lending eval and add a routing control for those generic terms.
|
🤖 Automated message from Kaan's Automated Triage Bot. Thanks — both fixes landed exactly right, and the extra negative-control scenario is a genuinely nice touch. I re-verified at
The three Nothing technical is open from my side. The listing decision stays with @kaankacar, because this adds XOXNO to the official |
Adds XOXNO Lending, a lending protocol live on Stellar mainnet, to the ecosystem catalog and the skill cards.
standards/ecosystem.md: entry under Lending & Borrowing with the controller and swap-router entry points, docs, SDK and OpenAPI specs, and a pointer to the XOXNO agent skill.site/src/data/skills.ts:ECOSYSTEM_CARDSentry forXOXNO/rs-lending-xlmskills/xoxno-lending/SKILL.md.evals/scenarios/standards/04-lending-protocols.json: routing scenario for lending-protocol questions.