[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70TZYWE48MTM8CGGDMWSJDN":3,"skill-same:01M70TZYWE48MTM8CGGDMWSJDN":79},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M70TZYWE48MTM8CGGDMWSJDN","plan-web3-game-assets",null,"Define an opt-in Ethereum, Base or Immutable game-asset lifecycle, including token identity, supply, rights, custody, game eligibility and chain-specific dependencies.","TimothyMeadows\u002FHephaera","TimothyMeadows","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4072037?v=4","01M6ERVE3WV9X55S1NT4W5FDGA","Timothy D Meadows II","01M6ERVE8H7CBATH6KYFDKG5CJ",4,"MIT","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fplan-web3-game-assets\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"plan","game assets","assets","plan web3 game assets","web3","game","identity","asset","ethereum","define","base","token","lifecycle","dependencies","chain","rights","immutable","opt","supply","2026-11-10 10:12:30",false,"---\nname: plan-web3-game-assets\ndescription: Define an opt-in Ethereum, Base or Immutable game-asset lifecycle, including token identity, supply, rights, custody, game eligibility and chain-specific dependencies.\nengines: [AGNOSTIC]\n---\n\n## When to use\n\nUse when a game needs blockchain-owned assets, NFT collections, transferable inventory or a Web3 asset economy. A visual asset request alone does not select blockchain integration.\n\n## Workflow\n\nRead the host `WEB3.md`, `web3-game.json` and the shared `.web3\u002FCONTRACT.md` when configured. Use `commands\u002Fweb3-game.sh registry` and local `inspect`, `validate` or `doctor`; these do not contact a chain. Preserve ENGINE, ARCHITECTURE, STYLE and independent media selection.\n\nDefine the actual lifecycle using [the asset brief](references\u002Fasset-brief.md). Separate card\u002Fitem definitions, unique instances or interchangeable quantities, wallet control, on-chain ownership, gameplay entitlement and content licenses. Keep authoritative game rules separate from arbitrary NFT metadata.\n\nHonor explicit Ethereum mainnet, Base or current Immutable selection. Refresh the dated chain\u002Fcompiler\u002Foperator facts from primary sources before production. Do not replace L1 with a cheaper chain or treat retired Immutable X as the EVM target. Disclose managed chain ingress\u002Foperator dependencies and optional hosted products separately.\n\nChoose the transfer-during-match rule before implementing admission. A snapshot license can permit an admitted match to finish after sale; a server reservation cannot stop external transfers. Strict exclusivity needs a reviewed contract-enforced lock\u002Fescrow with custody and recovery decisions. Never select custody silently.\n\nPrepare the complete proposed policy, asset\u002Fcontent ancestry, numerical limits and open production decisions for user review. Explicit `init --spec reviewed-spec.json` creates fresh host files; it neither proves approval nor selects services. Route contract, wallet, ownership, trading and lifecycle verification to their focused skills and resolve the selected engine's concrete integration owners.\n\n## Output\n\nReturn a reviewed lifecycle specification, exact chain\u002Fcollection\u002Fcontent identities, authority and dependency map, failure\u002Frecovery rules, evidence requirements and any unresolved decisions. Keep configuration and installation separate from signing, transactions, live deployment, asset promotion and release.\n","## When to use\n\nUse when a game needs blockchain-owned assets, NFT collections, transferable inventory or a Web3 asset economy. A visual asset request alone does not select blockchain integration.\n\n## Workflow\n\nRead the host `WEB3.md`, `web3-game.json` and the shared `.web3\u002FCONTRACT.md` when configured. Use `commands\u002Fweb3-game.sh registry` and local `inspect`, `validate` or `doctor`; these do not contact a chain. Preserve ENGINE, ARCHITECTURE, STYLE and independent media selection.\n\nDefine the actual lifecycle using [the asset brief](references\u002Fasset-brief.md). Separate card\u002Fitem definitions, unique instances or interchangeable quantities, wallet control, on-chain ownership, gameplay entitlement and content licenses. Keep authoritative game rules separate from arbitrary NFT metadata.\n\nHonor explicit Ethereum mainnet, Base or current Immutable selection. Refresh the dated chain\u002Fcompiler\u002Foperator facts from primary sources before production. Do not replace L1 with a cheaper chain or treat retired Immutable X as the EVM target. Disclose managed chain ingress\u002Foperator dependencies and optional hosted products separately.\n\nChoose the transfer-during-match rule before implementing admission. A snapshot license can permit an admitted match to finish after sale; a server reservation cannot stop external transfers. Strict exclusivity needs a reviewed contract-enforced lock\u002Fescrow with custody and recovery decisions. Never select custody silently.\n\nPrepare the complete proposed policy, asset\u002Fcontent ancestry, numerical limits and open production decisions for user review. Explicit `init --spec reviewed-spec.json` creates fresh host files; it neither proves approval nor selects services. Route contract, wallet, ownership, trading and lifecycle verification to their focused skills and resolve the selected engine's concrete integration owners.\n\n## Output\n\nReturn a reviewed lifecycle specification, exact chain\u002Fcollection\u002Fcontent identities, authority and dependency map, failure\u002Frecovery rules, evidence requirements and any unresolved decisions. Keep configuration and installation separate from signing, transactions, live deployment, asset promotion and release.\n",{"name":5,"engines":43,"description":7},[44],"AGNOSTIC","main","c88f4c5f7ece8057ad15e220a7020f8446e0ba80","skills\u002Fplan-web3-game-assets",3,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera","https:\u002F\u002Fhephaera.com\u002F","https:\u002F\u002Fgithub.com\u002FTimothyMeadows","http:\u002F\u002Fwww.timothymeadows.com","Software & AI Systems Architect | Distributed Systems & Agentic Platforms","2026-11-13 03:52:23",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add TimothyMeadows\u002FHephaera --skill plan-web3-game-assets",{"tool":61,"command":62},"bunx","bunx skills add TimothyMeadows\u002FHephaera --skill plan-web3-game-assets",{"tool":64,"command":65},"pnpm","pnpm dlx skills add TimothyMeadows\u002FHephaera --skill plan-web3-game-assets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fplan-web3-game-assets\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",262,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fplan-web3-game-assets\u002Fagents\u002Fopenai.yaml",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fasset-brief.md",2034,"https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fplan-web3-game-assets\u002Freferences\u002Fasset-brief.md",[80,101,122,141,160,179],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":38},"01M70V3EJ7JDFDFJ3XTKRGKRBP","verify-web3-game-lifecycle","Verify a game's selected Web3 asset, wallet, ownership and trading lifecycle with contract properties, canonical recovery, actual target evidence and separate release readiness.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fverify-web3-game-lifecycle\u002FSKILL.md",[],[24,87,31,88,23,89,90,91,92,93,94,95,96,97,98,26,99,100],"verify","verify web3 game lifecycle","with","evidence","readiness","release readiness","Wallet","recovery","properties","release","contract","canonical","ownership","trading",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M70V3CS767H4M1FP4C2A7K51","verify-onchain-game-assets","Verify exact on-chain game collection ownership and quantities at canonical blocks, reconcile inventory events, and design honest match admission. Use for ERC721\u002FERC1155 inventory, reorg recovery, reservations, or transfer-during-match rules.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fverify-onchain-game-assets\u002FSKILL.md",[],[24,108,87,20,21,109,33,110,111,112,113,114,115,116,117,118,94,119,120,121],"onchain","verify onchain game assets","for","inventory","reservations","design","erc721","use","Rules","collection","on-chain","at","blocks","reconcile",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":38},"01M70TYYZ7SPZ7PE6A6GQ5RXQ9","integrate-game-wallets","Integrate explicit player-wallet connection, scoped SIWE authentication, authority invalidation and reviewed target-specific handoff without application-held player keys.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fintegrate-game-wallets\u002FSKILL.md",[],[24,129,130,131,132,93,133,134,135,136,137,138,139,140],"integrate game wallets","integrate","wallets","siwe","keys","authentication","player","scoped","connection","authority","application","handoff",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":38},"01M70TYX656BP1R0KWMYRX437R","integrate-game-asset-trading","Integrate explicitly selected game asset settlement with exact unsigned intents, scoped approvals, idempotent operations and canonical receipt reconciliation. Use for NFT listing, buying, cancellation, retries or marketplace integration.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fintegrate-game-asset-trading\u002FSKILL.md",[],[24,148,130,26,100,149,150,110,136,151,115,152,153,89,154,155,156,157,158,159],"integrate game asset trading","reconciliation","idempotent operations","retries","listing","idempotent","nft","approvals","operations","marketplace","integration","intents",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":38},"01M70TWV3J83RAJMA7BC62CPAH","build-evm-game-contracts","Author and verify host-owned EVM game collections and explicit mint, burn, craft or admin rules with pinned Solidity tooling. Use for contract source and deployment candidates; deployment and player signing require separate authorization.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fbuild-evm-game-contracts\u002FSKILL.md",[],[24,167,168,169,170,110,171,135,172,97,173,115,116,174,89,175,176,87,177,178],"evm","build","build evm game contracts","contracts","deployment","collections","host","author","admin","signing","mint","tooling",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":190,"publishedAt":38},"01M6ES7KY8K93QWQ83R063FN6K","threejs-build-code-models","Author procedural Three.js TypeScript or JavaScript models from a text brief and optional authorized references using deterministic ordered review passes. Use when the selected art pipeline is CODE and the runtime model should be source code rather than a downloaded or generated mesh.","https:\u002F\u002Fgithub.com\u002FTimothyMeadows\u002FHephaera\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs-build-code-models\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":188,"taxonomyTypeDesc":189},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[191,168,192,193,194,195,196,197,198,199,200,201,202,203,204,115,205,206,207,208],"code","models","threejs build code models","Code Models","threejs","mesh","deterministic","brief","three","model","runtime","pipeline","Art","generated","review","text","javascript","references"]