[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BA528VF80AQJST38FSRC3":3,"skill-same:01M78BA528VF80AQJST38FSRC3":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78BA528VF80AQJST38FSRC3","robinhood-agent-forge",null,"Prepare, register, inspect, and safely operate chain-scoped AI agent identities on Robinhood Chain (EVM\u002FERC-8004-compatible) or Solana (SVM\u002FMetaplex Core) through Cheshire Terminal and the open-source robinhood-agents SDK. Use for chain selection, deployment verification, metadata, unsigned EVM registration intents, wallet-authorized sponsored Solana identity mints, ownership and authority review, reputation, validation, or guarded infrastructure deployment.","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: robinhood-agent-forge\ndescription: Prepare, register, inspect, and safely operate chain-scoped AI agent identities on Robinhood Chain (EVM\u002FERC-8004-compatible) or Solana (SVM\u002FMetaplex Core) through Cheshire Terminal and the open-source robinhood-agents SDK. Use for chain selection, deployment verification, metadata, unsigned EVM registration intents, wallet-authorized sponsored Solana identity mints, ownership and authority review, reputation, validation, or guarded infrastructure deployment.\n---\n\n# Robinhood Agent Forge\n\nOpen `https:\u002F\u002Fcheshireterminal.ai\u002Fagents\u002Fforge` for the canonical interactive flow. Ask the user to choose `Robinhood Chain` or `Solana` before preparing any write. Treat the result as one chain-scoped identity; never imply that a single token exists on both chains.\n\n## Choose rails\n\n- Choose **Robinhood Chain** for an ERC-721 identity in the deployed ERC-8004-compatible identity, reputation, and validation suite. Prefer testnet chain `46630`. Require an explicit mainnet confirmation for chain `4663` immediately before wallet submission.\n- Choose **Solana** for a Metaplex Core asset with Agent Identity. Prefer `POST \u002Fapi\u002Fmetaplex-agents\u002Fmint-prepare` (Metaplex API → user-signed tx) then `mint-confirm` (live feed). Treasury-sponsored `POST \u002Fapi\u002Fmetaplex-agents\u002Fmint` is the fallback. Use only the cluster returned by the current health response. Treat `mainnet-beta` as a live mainnet write and require explicit confirmation.\n- Choose **omni (both rails)** when the user wants Solana **and** Robinhood as one logical agent, optionally bound with LayerZero zk-omni (`dual_identity_link`). Use `planOmniAgentMint` \u002F CLI `omni-mint-plan` (skill `cheshire-omni-mint`, docs `docs\u002FOMNI_MINT.md`). Still two wallet-signed writes — never claim a single cross-chain NFT.\n- Create a separate identity if the user later chooses the other single rail alone. After dual mint, link with `planOmniIdentityLink` only after verifying control of both.\n\nRead [references\u002Fapi.md](references\u002Fapi.md) before calling Cheshire APIs, [references\u002Fsdk.md](references\u002Fsdk.md) before using the package, and [references\u002Fdeployment.md](references\u002Fdeployment.md) before trusting or deploying contracts.\n\n## Execute the lifecycle\n\n1. Fetch the selected rail's current capability response.\n2. Validate the network or cluster, trusted registry\u002Fprogram, signer availability, sponsorship policy, and exact owner and authority model.\n3. Collect the name, description, image, services, capabilities, and intended owner. Prefer durable `ipfs:\u002F\u002F` metadata for production.\n4. Normalize and prepare the complete action without receiving a private key.\n5. Show the user the chain, destination contract\u002Fprogram, decoded action, native value or sponsorship, metadata URI, owner, payer, update authority, freeze policy, and expected finality checks.\n6. Require fresh wallet authorization only after the review. Never reuse a signed Solana intent.\n7. Submit through the correct signer model: the EVM owner wallet broadcasts Robinhood calldata; for Solana prefer Metaplex API prepare → owner wallet signs and submits the tx → `mint-confirm` (treasury-sponsored mint remains a fallback).\n8. Verify the transaction and direct chain state. Report a Solana mint whose Agent Identity registration failed as partial success. Confirmed agents should appear on `\u002Fagents\u002Flive` (server publish and\u002For `POST \u002Fapi\u002Fagent-explorer\u002Freport`).\n\nNever request, store, print, or transmit a private key or seed phrase. Never silently switch a platform, network, wallet, registry, program, payer, authority, or metadata URI.\n\n## Preserve ownership semantics\n\n- Robinhood `register(agentURI)` mints the identity ERC-721 to `msg.sender` and initializes `agentWallet` to that same address. An ERC-721 transfer clears a nonzero `agentWallet`. An approval can transfer the identity and update metadata, so describe approvals as consequential authority.\n- Robinhood reputation feedback comes from non-authorized clients; an owner or approved operator cannot self-review. Validation requests require identity owner\u002Foperator authority and name a validator that alone may respond.\n- The hosted Solana route makes the user wallet the Core asset owner. The sponsoring treasury pays, remains update authority, and creates the asset frozen with a permanent freeze delegate. Show the exact treasury public key and policy before signature; stop if the current surface cannot disclose them.\n\n## Enforce the identity-token boundary\n\n- Robinhood Agent Forge currently registers an identity ERC-721 only. It does not deploy or mint a fungible ERC-20 agent token.\n- Solana identity mint (Metaplex Core + Agent Identity) is separate from fungible agent-token launch. Default posture for fungible agent-token launch is **production-paused** (`POST \u002Fapi\u002Fmetaplex-agents\u002Flaunch-token` must not be called while paused). When health reports `mintPolicy.fungibleAgentTokenLaunch === \"available\"`, wallet-owned agents may call that route with a durable idempotency key. Require ownership of the Core asset, review the unsigned tx, and never treat `setToken: true` as reversible.\n- Install or pin the open SDK with `npm install \"github:Solizardking\u002Frobinhood-agents#v0.1.0\"` (or the monorepo `robinhood-agents\u002F` package). Do not invent alternate registry namespaces.\n- Do not describe an identity or token as an investment or promise value, yield, liquidity, or price appreciation.\n\n## Deploy only for a new namespace\n\nThe canonical registry suites are already deployed on Robinhood testnet and mainnet. Do not rerun their deployer or create a competing Cheshire identity namespace. Registry deployment is an operator action; end-user `register(agentURI)` is a separate wallet action. Solana uses existing Metaplex programs and does not require a replacement program deployment for an identity mint.\n\n## Verify before claiming completion\n\n- On EVM, require a successful receipt from the intended identity registry, a matching `Registered` event, then matching direct `ownerOf`, `agentURI`, and `getAgentWallet` reads. A receipt alone is insufficient.\n- On Solana, the hosted route waits for `confirmed` commitment for both mint and registration transactions. Then fetch the Core asset and Agent Identity state. Call the identity complete only when the canonical fetch reports registration; otherwise preserve the mint signature and report partial success.\n- Treat direct chain reads as canonical. Treat Blockscout, DAS, and other indexers as discovery layers that may lag.\n- Do not claim deployment, source verification, registration, token launch, or finality without checking it.\n","# Robinhood Agent Forge\n\nOpen `https:\u002F\u002Fcheshireterminal.ai\u002Fagents\u002Fforge` for the canonical interactive flow. Ask the user to choose `Robinhood Chain` or `Solana` before preparing any write. Treat the result as one chain-scoped identity; never imply that a single token exists on both chains.\n\n## Choose rails\n\n- Choose **Robinhood Chain** for an ERC-721 identity in the deployed ERC-8004-compatible identity, reputation, and validation suite. Prefer testnet chain `46630`. Require an explicit mainnet confirmation for chain `4663` immediately before wallet submission.\n- Choose **Solana** for a Metaplex Core asset with Agent Identity. Prefer `POST \u002Fapi\u002Fmetaplex-agents\u002Fmint-prepare` (Metaplex API → user-signed tx) then `mint-confirm` (live feed). Treasury-sponsored `POST \u002Fapi\u002Fmetaplex-agents\u002Fmint` is the fallback. Use only the cluster returned by the current health response. Treat `mainnet-beta` as a live mainnet write and require explicit confirmation.\n- Choose **omni (both rails)** when the user wants Solana **and** Robinhood as one logical agent, optionally bound with LayerZero zk-omni (`dual_identity_link`). Use `planOmniAgentMint` \u002F CLI `omni-mint-plan` (skill `cheshire-omni-mint`, docs `docs\u002FOMNI_MINT.md`). Still two wallet-signed writes — never claim a single cross-chain NFT.\n- Create a separate identity if the user later chooses the other single rail alone. After dual mint, link with `planOmniIdentityLink` only after verifying control of both.\n\nRead [references\u002Fapi.md](references\u002Fapi.md) before calling Cheshire APIs, [references\u002Fsdk.md](references\u002Fsdk.md) before using the package, and [references\u002Fdeployment.md](references\u002Fdeployment.md) before trusting or deploying contracts.\n\n## Execute the lifecycle\n\n1. Fetch the selected rail's current capability response.\n2. Validate the network or cluster, trusted registry\u002Fprogram, signer availability, sponsorship policy, and exact owner and authority model.\n3. Collect the name, description, image, services, capabilities, and intended owner. Prefer durable `ipfs:\u002F\u002F` metadata for production.\n4. Normalize and prepare the complete action without receiving a private key.\n5. Show the user the chain, destination contract\u002Fprogram, decoded action, native value or sponsorship, metadata URI, owner, payer, update authority, freeze policy, and expected finality checks.\n6. Require fresh wallet authorization only after the review. Never reuse a signed Solana intent.\n7. Submit through the correct signer model: the EVM owner wallet broadcasts Robinhood calldata; for Solana prefer Metaplex API prepare → owner wallet signs and submits the tx → `mint-confirm` (treasury-sponsored mint remains a fallback).\n8. Verify the transaction and direct chain state. Report a Solana mint whose Agent Identity registration failed as partial success. Confirmed agents should appear on `\u002Fagents\u002Flive` (server publish and\u002For `POST \u002Fapi\u002Fagent-explorer\u002Freport`).\n\nNever request, store, print, or transmit a private key or seed phrase. Never silently switch a platform, network, wallet, registry, program, payer, authority, or metadata URI.\n\n## Preserve ownership semantics\n\n- Robinhood `register(agentURI)` mints the identity ERC-721 to `msg.sender` and initializes `agentWallet` to that same address. An ERC-721 transfer clears a nonzero `agentWallet`. An approval can transfer the identity and update metadata, so describe approvals as consequential authority.\n- Robinhood reputation feedback comes from non-authorized clients; an owner or approved operator cannot self-review. Validation requests require identity owner\u002Foperator authority and name a validator that alone may respond.\n- The hosted Solana route makes the user wallet the Core asset owner. The sponsoring treasury pays, remains update authority, and creates the asset frozen with a permanent freeze delegate. Show the exact treasury public key and policy before signature; stop if the current surface cannot disclose them.\n\n## Enforce the identity-token boundary\n\n- Robinhood Agent Forge currently registers an identity ERC-721 only. It does not deploy or mint a fungible ERC-20 agent token.\n- Solana identity mint (Metaplex Core + Agent Identity) is separate from fungible agent-token launch. Default posture for fungible agent-token launch is **production-paused** (`POST \u002Fapi\u002Fmetaplex-agents\u002Flaunch-token` must not be called while paused). When health reports `mintPolicy.fungibleAgentTokenLaunch === \"available\"`, wallet-owned agents may call that route with a durable idempotency key. Require ownership of the Core asset, review the unsigned tx, and never treat `setToken: true` as reversible.\n- Install or pin the open SDK with `npm install \"github:Solizardking\u002Frobinhood-agents#v0.1.0\"` (or the monorepo `robinhood-agents\u002F` package). Do not invent alternate registry namespaces.\n- Do not describe an identity or token as an investment or promise value, yield, liquidity, or price appreciation.\n\n## Deploy only for a new namespace\n\nThe canonical registry suites are already deployed on Robinhood testnet and mainnet. Do not rerun their deployer or create a competing Cheshire identity namespace. Registry deployment is an operator action; end-user `register(agentURI)` is a separate wallet action. Solana uses existing Metaplex programs and does not require a replacement program deployment for an identity mint.\n\n## Verify before claiming completion\n\n- On EVM, require a successful receipt from the intended identity registry, a matching `Registered` event, then matching direct `ownerOf`, `agentURI`, and `getAgentWallet` reads. A receipt alone is insufficient.\n- On Solana, the hosted route waits for `confirmed` commitment for both mint and registration transactions. Then fetch the Core asset and Agent Identity state. Call the identity complete only when the canonical fetch reports registration; otherwise preserve the mint signature and report partial success.\n- Treat direct chain reads as canonical. Treat Blockscout, DAS, and other indexers as discovery layers that may lag.\n- Do not claim deployment, source verification, registration, token launch, or finality without checking it.\n",{"name":5,"description":7},"main","be3de0244dc1a57e323d8160787ebb40fb64930e","public\u002Fapi\u002Fskills\u002Frobinhood-agent-forge","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Solizardking\u002Fskillhub-main --skill robinhood-agent-forge",{"tool":39,"command":40},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill robinhood-agent-forge",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill robinhood-agent-forge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",300,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"metadata.json",650,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Fmetadata.json",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fapi.md",11216,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Freferences\u002Fapi.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdeployment.md",5538,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Freferences\u002Fdeployment.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsdk.md",6654,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Freferences\u002Fsdk.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"verification.json",1978,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Frobinhood-agent-forge\u002Fverification.json",[74,81,88,95,102,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]