Skip to content

Add RELAY task-market onboarding to community skills - #188

Merged
stellar-triage-bot[bot] merged 2 commits into
stellar:mainfrom
yssoft-gif:patch-1
Nov 17, 2026
Merged

stellar-triage-bot[bot] merged 2 commits into
stellar:mainfrom
yssoft-gif:patch-1

Conversation

@yssoft-gif

Copy link
Copy Markdown
Contributor

Add RELAY Task Market to the community section by appending one entry to ECOSYSTEM_CARD_SOURCES, preserving existing order and all first-party skills.

The external Markdown teaches an agent operator to download the two public clients, install the pinned Stellar SDK, and run a no-funding encrypted snapshot trial with a disposable in-memory signing key. It then documents scoped requests, offers, acceptance, encrypted-file delivery and direct XLM settlement. The trial needs no existing wallet, funded account, trustline or Site token and cannot publish business records or send funds.

Validation:

  • Published Markdown URL returns HTTP 200 and matches the approved deployed source
  • Frontmatter includes name: relay-task-market and a workflow description
  • Public Node 22+ trial was checked on the live release without sending funds
  • Proposed change is 8 additions and 0 deletions in one data file; no generated files or existing cards changed

This is custom encrypted HTTP, not an A2A or x402 implementation. The guide explicitly distinguishes mainnet XLM from not-yet-ready USDC receipt and inactive escrow. We do not yet have independently verified paid customer trades.

Disclosure: I operate RELAY; prepared with automated assistance. This is a community listing request for review, not a claim of Stellar endorsement.

Append one externally hosted community card. The published Markdown includes a no-funding encrypted snapshot trial and direct XLM task-settlement guidance; no existing cards or first-party skills are changed.
@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

👀 Picked this up — a review will follow shortly.

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Thanks for this, and for the clear disclosure. The guide is unusually careful. It names its limits plainly, and the client code matches what it claims.

What I checked:

  • The card is a clean append to ECOSYSTEM_CARD_SOURCES and merges cleanly with main.
  • Every URL in the skill returns 200. The frontmatter is valid.
  • The pinned USDC issuer is Circle's mainnet issuer on Horizon.
  • I read market_agent.mjs. The key comes only from STELLAR_SECRET_KEY. Nothing is submitted without a bare --broadcast. --trial uses a random in-memory key and accepts only --site.

Before this goes on the catalog, please change two things:

  1. A stable public home. The card points at agent-relay-lab-20261116.twincactus4.chatgpt.site, a dated lab subdomain on a shared host. There is no public source repo. Please put the SKILL.md and the client source in a public GitHub repo. Then point copyValue at its raw.githubusercontent.com URL, like the other cards.
  2. Pinned clients. The skill tells agents to download and run market_agent.mjs and agent_transport.mjs from a mutable URL. In normal use, these scripts hold a mainnet secret key. Please serve them from a tagged release or a commit, and list a SHA-256 checksum for each in the skill. Then an agent can check the files before it runs them.

A small note, not a blocker: the English skill sends readers to market_guide.md for the full commands, but that guide is in Korean. An English version would help most agents.

If a GitHub repo is not possible for you, tell us here. A maintainer will then decide on the current host.

Address the catalog review: publish both local clients in yssoft-gif/relay-agent-client, pin downloads to commit ca7798fc4ec2c5c841b13f0494f55861d03d7bb1, publish SHA-256 verification and a full English guide, and point copyValue to immutable documentation commit c4bae7df04dbe99b23b1b071b4ef0ad0a7b65584.
@yssoft-gif

Copy link
Copy Markdown
Contributor Author

Addressed in 765d4b1.

I fetched the immutable public client URLs and verified both files byte-for-byte against the reviewed source. The public repo contains only the already-public local clients, checksum manifest and guides; no hosted server source, runtime configuration or customer records. No funds were sent.

Please re-review the updated card and pinned onboarding.

@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Thanks for the fast turnaround. The new repo is clean, and both review points are fixed.

What I checked at 765d4b1:

  • copyValue resolves at the pinned commit. The SKILL.md frontmatter is valid, and the English guide link resolves.
  • Both pinned client files match the SHA-256 values in the skill.
  • I read both clients again. The key comes only from STELLAR_SECRET_KEY. Payment needs a bare --broadcast. --trial uses a random in-memory key.
  • The USDC issuer is Circle's mainnet issuer on Horizon. @stellar/stellar-sdk@17.4.0 exports ./base.

One small change: pathLabel was "RELAY agent onboarding". Every other card uses owner/repo. Your fork does not allow maintainer edits, so I opened #189. It keeps your two commits and adds one commit that sets pathLabel to yssoft-gif/relay-agent-client. When #189 merges, this PR closes.

A note, not a blocker: @stellar/stellar-sdk@17.4.0 needs Node 22.12 or later. The skill says "Node.js 22 or later".

stellar-triage-bot Bot added a commit that referenced this pull request Nov 17, 2026
Add RELAY task-market onboarding to community skills (carries #188)
@stellar-triage-bot
stellar-triage-bot Bot merged commit 765d4b1 into stellar:main Nov 17, 2026
2 checks passed
@stellar-triage-bot

Copy link
Copy Markdown
Contributor

🤖 Automated message from the Stellar Triage Bot.

Your card merged through #189 with your two commits. It is now live on skills.stellar.org. Thanks for the quick fixes.

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.

1 participant