Skip to content

feat: add myriad — BNB Chain prediction market trading agent#15

Merged
kevarifin14 merged 7 commits into
moonpay:mainfrom
tonyagents:add-myriad-skill
Mar 19, 2026
Merged

feat: add myriad — BNB Chain prediction market trading agent#15
kevarifin14 merged 7 commits into
moonpay:mainfrom
tonyagents:add-myriad-skill

Conversation

@tonyagents

Copy link
Copy Markdown
Contributor

New Skill

Skill name: skills/myriad/

Description: AI trading agent for Myriad prediction markets on BNB Chain — discover markets, execute trades, claim winnings, and run as an MCP server for multi-agent workflows.

Primary chain: BNB Chain (chainId=56)
Primary token: USDT / USD1

Checklist

  • skills/myriad/SKILL.md with YAML frontmatter (name, description)
  • Skill added to .claude-plugin/marketplace.json
  • Description is specific about when Claude should trigger this skill

What it does

@myriadmarkets/cli gives AI agents a full prediction market trading loop on BNB Chain:

  • myriad markets list --keyword <topic> — discover live markets by topic, sorted by volume
  • myriad trade buy/sell --dry-run — preview then execute positions
  • myriad portfolio + myriad wallet balances — monitor exposure
  • myriad claim all — sweep resolved winning positions
  • myriad mcp — run as MCP server for Claude Code multi-agent orchestration

MoonPay Integration

Same pattern as other trading skills — MoonPay wallet becomes the Myriad trading wallet:

  1. mp wallet create --name "myriad-agent" — create BNB Chain wallet
  2. mp buy --token usdt_bsc --amount 100 ... — fund with USDT on BNB Chain
  3. mp wallet export --wallet "myriad-agent" — export private key
  4. myriad wallet setup — paste key (stored encrypted in OS keychain)
  5. Trade, claim, then mp virtual-account offramp to withdraw winnings to bank

Agent Patterns Covered

  • Event-driven trader: news catalyst → keyword scan → dry-run → execute
  • Portfolio monitor: check exposure + balances before each cycle
  • Winnings sweeper: myriad claim all on a schedule
  • Multi-agent desk: MCP server mode for scout + execution agent separation

@kevarifin14 kevarifin14 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.

Skill Review: skills/myriad/

Thanks for this contribution. The skill is well-written overall — clear structure, good CLI examples, solid end-to-end workflow, and the npm package (@myriadmarkets/cli@0.1.4) checks out. That said, I have several issues to flag before this can be merged.


1. Naming Convention Violation (blocking)

Per the repo's CLAUDE.md:

Partner skills: skills/{partner}-{name}/ (e.g., corbits-marketplace, dune-analytics)

The skill directory is skills/myriad/ — it should follow the {partner}-{name} pattern, e.g. skills/myriad-prediction-markets/ or skills/myriad-trading/. A bare partner name without a descriptive suffix breaks the naming convention every other skill in this repo follows.

The name field in the YAML frontmatter should be updated to match (e.g. myriad-prediction-markets).

2. marketplace.json: Skill listed inside moonpay-skills plugin (blocking)

The new skill is added to the moonpay-skills.skills[] array alongside all the ./skills/moonpay-* entries. This is a partner skill, not a MoonPay skill. It should either:

  • Be listed under its own separate plugin entry in the plugins array (like how moonpay-skills is its own plugin), or
  • At minimum, this should be discussed — lumping a third-party partner skill into the moonpay-skills plugin misrepresents ownership and muddies the plugin boundary.

3. Unrelated diff in marketplace.json

The PR sneaks in a dash-to-em-dash change ( to ) in the existing moonpay-skills description. This is unrelated to the skill being added and should be dropped or split into a separate PR to keep the diff clean.

4. Missing Prerequisites section

The template (template/SKILL.md) specifies a Prerequisites section listing required setup (MoonPay CLI installed, authenticated, etc.). This skill jumps straight from Overview to Installation. It should have an explicit Prerequisites section calling out:

  • Node.js / npm
  • MoonPay CLI installed and authenticated (mp login)
  • A funded BNB Chain wallet
  • @myriadmarkets/cli installed

5. Related Skills — verify these exist

The skill references:

  • moonpay-prediction-market — exists
  • scoutdoes not exist in this repo. There is no skills/scout/ directory. Remove this reference or file a separate PR adding it.
  • moonpay-check-wallet — exists
  • moonpay-swap-tokens — exists

Referencing a nonexistent skill is misleading to agents that try to load it.

6. myriad skills install --target claude — clarify scope

The "Skills (Claude / OpenClaw)" section mentions myriad skills install --target claude. This seems to install Myriad's own skill definitions into Claude Code, which is a different mechanism than this repo's marketplace. This could confuse agents about which skill source to use. At minimum, add a note clarifying the relationship (e.g., "This installs Myriad's built-in agent skills separately from the MoonPay skills marketplace").

7. Config path not under ~/.config/myriad/

The CLAUDE.md convention says skills instruct agents to use config files under ~/.config/ (e.g., ~/.config/moonpay/). The skill mentions ~/.config/myriad/config.json which is good, but also mentions "encrypts key to file + OS keychain" without specifying where that file lives. Be explicit about the config file path so agents can verify/debug.

8. Minor: myriad wallet deposit and myriad swap lack detail

These commands appear in the Setup and Portfolio sections but have no flags, options, or explanation of what they do. For an agent skill, every command should be actionable — what token does deposit expect? From where? What does swap swap, and with what parameters? Either flesh these out or remove them to avoid agents invoking commands blindly.


What's good

  • The YAML frontmatter description is specific and trigger-worthy — it clearly describes when an agent should load this skill.
  • Tags are relevant and well-chosen.
  • The agent patterns section (event-driven trader, portfolio monitor, etc.) is genuinely useful for agent orchestration.
  • The end-to-end workflow is clear and complete.
  • The MoonPay integration section is thorough and follows the same pattern as other trading skills.
  • The --dry-run emphasis is a great safety practice.

Summary: The skill content is high quality, but the naming convention and marketplace.json placement need to be fixed before merge. The nonexistent scout skill reference should be removed, and the minor issues above would strengthen the skill further.

@kevarifin14 kevarifin14 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.

Grade: B

Best of the partner skill submissions. Real npm package, clear CLI examples, good end-to-end workflow. Blocked by naming convention (myriad/myriad-prediction-markets/), marketplace.json misplacement, and a reference to a nonexistent scout skill. Fix those and this is close to mergeable.

@kevarifin14 kevarifin14 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.

Re-review after fixes (3 new commits)

Issues addressed:

  • ✅ Renamed skills/myriad/skills/myriad-prediction-markets/
  • ✅ Scout skill reference removed

Verification results:

  • @myriadmarkets/cli — confirmed real (npm, v0.1.4, 5 versions, MIT license)
  • clawhub — confirmed real (npm, v0.8.0)

Updated grade: B+

To get to A+, fix these:

  1. marketplace.json placement — Move the skill out of the moonpay-skills array and into its own plugin block:
{
  "name": "myriad-skills",
  "description": "BNB Chain prediction market trading via Myriad Markets CLI",
  "source": "./",
  "strict": false,
  "skills": [
    "./skills/myriad-prediction-markets"
  ]
}
  1. Unrelated diff — Drop the em-dash change in the existing moonpay-skills description. Keep the diff clean.
  2. mp wallet export security note — The skill instructs exporting a private key to set as an env var. Add a warning like: "⚠️ Your private key gives full access to your wallet. Never share it or commit it to version control."

@kevarifin14 kevarifin14 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.

Re-review: Grade A-

Issues fixed:

  • ✅ Own myriad-skills plugin block in marketplace.json
  • ✅ Em-dash diff clean

Verified: @myriadmarkets/cli (npm v0.1.4, real), clawhub (npm v0.8.0, real).

One remaining issue for A+:

  • Security warning for private key export — The skill instructs mp wallet export and setting MYRIAD_PRIVATE_KEY. Add a warning like:

⚠️ Security: Your private key gives full control of your wallet. Use a dedicated wallet with limited funds for trading. Never commit private keys to version control.

Add that and this is A+.

@kevarifin14 kevarifin14 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.

Grade: A+

All issues resolved:

  • ✅ Own myriad-skills plugin block
  • ✅ Em-dash diff clean
  • ✅ Security warning added for private key export — warns about full wallet access, never commit, never reuse across services
  • ✅ Encrypted key storage via myriad wallet setup

Verified: @myriadmarkets/cli (npm v0.1.4), clawhub (npm v0.8.0).

Ready to merge.

@kevarifin14 kevarifin14 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.

Approved as A+, but there's a merge conflict in marketplace.json from PRs #8 and #9 being merged. Please rebase on main to resolve and I'll merge immediately.

@kevarifin14 kevarifin14 merged commit 5957521 into moonpay:main Mar 19, 2026
3 checks passed
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.

2 participants