[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M92RQN0D4GJ94Q8FDPF7DF":3,"skill-same:01M6M92RQN0D4GJ94Q8FDPF7DF":112},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6M92RQN0D4GJ94Q8FDPF7DF","android-app-factory",null,"Suede AI Android App Factory Skills. Use when asked to \"build an Android app\" or modernize a Kotlin\u002FCompose product: architecture, policy, privacy, billing, tests and a Play-ready release evidence package. NOT FOR: Play uploads or rollout (suede-play-release), website-to-iOS conversion (site-to-ios-app), review-only work (suede-code), or store listing strategy (suede-aso).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"android","android app factory","app","factory","listing","review","when","for","billing","conversion","compose","ready","evidence","only","rollout","work","aso","website","product","release","code","architecture","2026-11-10 10:12:30",false,"---\nname: android-app-factory\ndescription: \"Suede AI Android App Factory Skills. Use when asked to \\\"build an Android app\\\" or modernize a Kotlin\u002FCompose product: architecture, policy, privacy, billing, tests and a Play-ready release evidence package. NOT FOR: Play uploads or rollout (suede-play-release), website-to-iOS conversion (site-to-ios-app), review-only work (suede-code), or store listing strategy (suede-aso).\"\nmetadata:\n  display-name: \"Suede AI Android App Factory Skills\"\n---\n\n# Suede AI Android App Factory Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nAgent with repo read\u002Fwrite and shell access; Android SDK\u002FJDK and project Gradle toolchain for builds, emulator\u002Fdevice for runtime proof, web access for current official Play policy.\n\n```\nIron Law: no release-ready claim without a signed `bundleRelease` plus a live\nPlay Console check, not a debug build, screenshot, source read, or upload.\n```\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n## Principle\n\nBuild the product, policy evidence, and Play listing together. A successful\nrelease is an installable and usable app whose claims, disclosures,\nentitlements, privacy behavior, and store configuration agree.\n\n## Source Truth and Freshness\n\nAt the start of every release-oriented run:\n\n1. Identify the exact repo, package\u002Fapplication ID, branch, Play app, target\n   track, and whether the checkout is dirty.\n2. Read `references\u002Fplay-policy-baseline.md`.\n3. Re-open the linked official Google sources for any submission-sensitive\n   requirement. Record the URL, observed requirement, and check time in\n   `assets\u002Fandroid-release-gate.template.md`.\n4. Treat current repo code and the live Play Console as source truth for the\n   app. Treat the reference date as a baseline, not permanent policy.\n\nTake the target-SDK default and enforcement dates from the baseline file, never\nfrom memory. As of the 2026-10-23 baseline, phone and tablet submissions must\ntarget API 36 (extensions end 2026-11-01) and use Play Billing Library 8 or\nlater. Recheck every run: form-factor exceptions and dates differ, and Google\nannounces the next year's level each spring.\n\n## Delivery Contract\n\nLock these before implementation:\n\n- user and one core outcome;\n- supported form factors, devices, locales, minimum SDK, and offline behavior;\n- application ID, ownership, signing model, Play app\u002Ftrack, and release owner;\n- data inventory, third-party SDKs, permissions, account model, deletion path,\n  privacy policy owner, and Data Safety owner;\n- monetization and entitlement source truth, or an explicit free-v1 decision;\n- architecture and migration constraints;\n- acceptance devices\u002FAPI levels, tests, performance\u002Faccessibility targets,\n  store artifacts, and release evidence;\n- external mutations requiring confirmation: product creation, credential use,\n  Play upload, track promotion, staged rollout, or production release.\n\nUnknowns stay unknown. Never invent a package name, product ID, policy answer,\nprivacy URL, customer claim, or Play Console state.\n\n## Production Pipeline\n\n1. **Validate the product**: define the user outcome and evidence of demand.\n   Treat keyword research as one input, not proof of product-market fit.\n2. **Verify policy**: capture current target-SDK and form-factor rules, app\n   access requirements, Data Safety scope, content rating, account deletion,\n   billing policy, and any permission-specific declarations.\n3. **Design architecture and risk**: use the smallest maintainable architecture\n   that preserves unidirectional state, lifecycle safety, offline\u002Ferror\u002Floading\n   states, test seams, and a least-data\u002Fleast-permission posture.\n4. **Scaffold**: native Kotlin + Jetpack Compose by default. Resolve current\n   stable Android\u002FJetpack versions from official sources, lock them in a version\n   catalog, and prove a debug build before feature work.\n5. **Build the core loop**: implement one complete user outcome with real or\n   deterministic demo data. Add history, saved state, sync, or accounts only\n   when the product contract requires them.\n6. **Prove quality**: unit, repository, ViewModel, Compose UI\u002Finstrumented,\n   accessibility, and end-to-end core-loop tests as applicable; static analysis,\n   release build, device\u002FAPI matrix, baseline profile, and Macrobenchmark.\n7. **Add monetization safely**: use Play Billing for covered digital goods,\n   process pending purchases, verify and acknowledge purchases after entitlement\n   handling, restore ownership, and keep secrets\u002Fserver verification off-device.\n8. **Complete trust surfaces**: privacy policy, Data Safety, SDK data behavior,\n   permission rationale, in-app and web account deletion when accounts exist,\n   content rating, ads declarations, app access instructions, and Play Integrity\n   only where abuse risk justifies it.\n9. **Build store artifacts**: truthful listing, icon\u002Ffeature graphic,\n   screenshots for every declared form factor, localization, support contact,\n   release notes, and reviewer instructions. Route title, short description,\n   keyword coverage, and screenshot sequencing to `suede-aso`; a listing that\n   passes review but cannot be found ships nothing.\n10. **Hand off to release**: signed AAB, Play App Signing, completed release\n    gate, then `suede-play-release` for credential preflight, testing-track\n    upload, promotion, staged rollout, and the live track readback.\n\nRead these before building:\n\n- `references\u002Fandroid-factory-pipeline.md`: phase artifacts and release flow;\n- `references\u002Farchitecture-and-quality.md`: architecture, tests,\n  accessibility, performance, and build checks;\n- `references\u002Fprivacy-billing-integrity.md`: privacy, Data Safety, account\n  deletion, Billing, and Integrity controls;\n- `references\u002Fplay-policy-baseline.md`: dated official-policy baseline;\n- `references\u002Fkids-and-family-apps.md`: before building anything whose\n  audience includes children (StoryBeam-style reading apps, beginner lesson\n  apps such as GuitarHub for young players).\n\n## Kids and family apps\n\nWhen the target audience includes children under 13, the Families policy and\nchildren's privacy law shape the architecture, so settle them in the Delivery\nContract, not at listing time:\n\n- Collect no personal data from children: no child accounts, no free-text\n  fields that could capture a name, school, or location, no voice or photo\n  capture, no advertising ID, no precise location.\n- Use only SDKs that are allowed in Families apps, and no ads SDK that is not\n  Families self-certified. No analytics that send persistent identifiers.\n- Keep every story, image, and sound age-appropriate for the declared band,\n  including AI-generated content, with a screening step before display.\n- Put purchases, external links, and settings behind a parental gate.\n\nA conflict with these is an extreme-risk finding under the gate policy.\n\n## Public-Safe Defaults\n\n- Use placeholder IDs such as `com.example.product` until ownership is verified.\n- Keep upload keys, passwords, service-account JSON, API secrets, and production\n  identifiers outside Git; use local\u002FCI secret stores and prove ignore rules.\n- Use Play App Signing and a distinct upload key.\n- Prefer a free v1 when Billing would delay validation, but do not bypass Play\n  Billing for covered digital goods.\n- Collect no data and request no permission without a stated product purpose,\n  retention\u002Fdeletion rule, disclosure path, and test.\n- Treat Play Integrity as an abuse signal, not authentication and not the sole\n  basis for a permanent block.\n- Keep submission and rollout actions human-confirmed and reversible where the\n  platform permits.\n\n## Release Gate\n\nCopy `assets\u002Fandroid-release-gate.template.md` into the app repo and complete it\nwith links or command output. Recommend `hold` when any required item lacks\nevidence, including:\n\n- target policy was not checked live or the build targets the wrong API\u002Fform\n  factor;\n- a release targeting Android 15+ has not been verified for 16 KB page-size\n  compatibility on 64-bit devices, including transitive native SDKs;\n- `test`, lint\u002Fstatic analysis, `assembleRelease`, or `bundleRelease` fails;\n- the core loop fails on the declared device\u002FAPI matrix or offline\u002Ferror path;\n- accessibility checks, large text, TalkBack, keyboard\u002Fswitch access, contrast,\n  or reduced-motion behavior have launch-critical failures;\n- performance evidence is missing for startup or the core task, or a known\n  regression exceeds the product budget without approval;\n- Data Safety, privacy policy, permissions, account deletion, content rating,\n  ads, app access, or SDK behavior disagree;\n- Billing runs on a Billing Library version Play no longer accepts, or\n  entitlement, pending, restore\u002Frequery, acknowledgement, cancellation,\n  refund\u002Frevocation, or backend verification behavior is unproven when relevant;\n- a child-directed app collects personal data, ships a non-Families ads SDK, or\n  shows content outside its declared age band;\n- secrets or signing material are committed, or Play App Signing\u002Fupload-key\n  ownership, developer verification, or package registration is unresolved;\n- listing claims or screenshots show behavior not present in the release build;\n- a Play upload, track promotion, or rollout lacks explicit user confirmation.\n\nReturn one gate: `ship`, `ship-with-caveats`, or `hold`. A caveat must have an\nowner, risk, and next action; policy, security, privacy, billing, crash, and\ncore-task blockers cannot be downgraded to cosmetic caveats.\n\n## Routing\n\n- Existing-app findings-only review → `suede-code --findings-only`.\n- CI implementation around the release evidence → `suede-ci-gate`.\n- Coordinated architecture, product, policy, store, and QA lanes →\n  `suede-agent-teams` with exclusive file ownership and a serialized release\n  lane.\n- Play upload, track promotion, staged rollout, live-state readback →\n  `suede-play-release`.\n- Play listing, keywords, screenshots, ratings → `suede-aso`.\n- Same product from an existing website on iOS → `site-to-ios-app`. A native\n  iOS build with no website is a private Suede AI companion, not in this pack.\n\n## Boundaries\n\n- Do not submit, create products, change pricing, promote tracks, or start a\n  production rollout without explicit confirmation.\n- Do not answer Play policy or Data Safety questions from memory when live\n  official guidance or the Play Console is available.\n- Do not claim release-ready from a debug build, screenshot, local source\n  inspection, or successful upload alone.\n- Do not use Play Integrity as a substitute for server authorization, purchase\n  verification, rate limits, fraud operations, or an appeal path.\n- Do not call a Data Safety form complete until first-party code and every\n  included SDK have been inventoried against actual release behavior.\n- When a confirmation gate fires (product creation, credential use, upload,\n  track promotion, rollout, production release), halt: name the exact package\n  ID, track, and rollout percentage, offer 2-4 options, and wait. Irreversible\n  public action is the gate policy's single exception; the user's choice is final.\n","# Suede AI Android App Factory Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nAgent with repo read\u002Fwrite and shell access; Android SDK\u002FJDK and project Gradle toolchain for builds, emulator\u002Fdevice for runtime proof, web access for current official Play policy.\n\n```\nIron Law: no release-ready claim without a signed `bundleRelease` plus a live\nPlay Console check, not a debug build, screenshot, source read, or upload.\n```\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n## Principle\n\nBuild the product, policy evidence, and Play listing together. A successful\nrelease is an installable and usable app whose claims, disclosures,\nentitlements, privacy behavior, and store configuration agree.\n\n## Source Truth and Freshness\n\nAt the start of every release-oriented run:\n\n1. Identify the exact repo, package\u002Fapplication ID, branch, Play app, target\n   track, and whether the checkout is dirty.\n2. Read `references\u002Fplay-policy-baseline.md`.\n3. Re-open the linked official Google sources for any submission-sensitive\n   requirement. Record the URL, observed requirement, and check time in\n   `assets\u002Fandroid-release-gate.template.md`.\n4. Treat current repo code and the live Play Console as source truth for the\n   app. Treat the reference date as a baseline, not permanent policy.\n\nTake the target-SDK default and enforcement dates from the baseline file, never\nfrom memory. As of the 2026-10-23 baseline, phone and tablet submissions must\ntarget API 36 (extensions end 2026-11-01) and use Play Billing Library 8 or\nlater. Recheck every run: form-factor exceptions and dates differ, and Google\nannounces the next year's level each spring.\n\n## Delivery Contract\n\nLock these before implementation:\n\n- user and one core outcome;\n- supported form factors, devices, locales, minimum SDK, and offline behavior;\n- application ID, ownership, signing model, Play app\u002Ftrack, and release owner;\n- data inventory, third-party SDKs, permissions, account model, deletion path,\n  privacy policy owner, and Data Safety owner;\n- monetization and entitlement source truth, or an explicit free-v1 decision;\n- architecture and migration constraints;\n- acceptance devices\u002FAPI levels, tests, performance\u002Faccessibility targets,\n  store artifacts, and release evidence;\n- external mutations requiring confirmation: product creation, credential use,\n  Play upload, track promotion, staged rollout, or production release.\n\nUnknowns stay unknown. Never invent a package name, product ID, policy answer,\nprivacy URL, customer claim, or Play Console state.\n\n## Production Pipeline\n\n1. **Validate the product**: define the user outcome and evidence of demand.\n   Treat keyword research as one input, not proof of product-market fit.\n2. **Verify policy**: capture current target-SDK and form-factor rules, app\n   access requirements, Data Safety scope, content rating, account deletion,\n   billing policy, and any permission-specific declarations.\n3. **Design architecture and risk**: use the smallest maintainable architecture\n   that preserves unidirectional state, lifecycle safety, offline\u002Ferror\u002Floading\n   states, test seams, and a least-data\u002Fleast-permission posture.\n4. **Scaffold**: native Kotlin + Jetpack Compose by default. Resolve current\n   stable Android\u002FJetpack versions from official sources, lock them in a version\n   catalog, and prove a debug build before feature work.\n5. **Build the core loop**: implement one complete user outcome with real or\n   deterministic demo data. Add history, saved state, sync, or accounts only\n   when the product contract requires them.\n6. **Prove quality**: unit, repository, ViewModel, Compose UI\u002Finstrumented,\n   accessibility, and end-to-end core-loop tests as applicable; static analysis,\n   release build, device\u002FAPI matrix, baseline profile, and Macrobenchmark.\n7. **Add monetization safely**: use Play Billing for covered digital goods,\n   process pending purchases, verify and acknowledge purchases after entitlement\n   handling, restore ownership, and keep secrets\u002Fserver verification off-device.\n8. **Complete trust surfaces**: privacy policy, Data Safety, SDK data behavior,\n   permission rationale, in-app and web account deletion when accounts exist,\n   content rating, ads declarations, app access instructions, and Play Integrity\n   only where abuse risk justifies it.\n9. **Build store artifacts**: truthful listing, icon\u002Ffeature graphic,\n   screenshots for every declared form factor, localization, support contact,\n   release notes, and reviewer instructions. Route title, short description,\n   keyword coverage, and screenshot sequencing to `suede-aso`; a listing that\n   passes review but cannot be found ships nothing.\n10. **Hand off to release**: signed AAB, Play App Signing, completed release\n    gate, then `suede-play-release` for credential preflight, testing-track\n    upload, promotion, staged rollout, and the live track readback.\n\nRead these before building:\n\n- `references\u002Fandroid-factory-pipeline.md`: phase artifacts and release flow;\n- `references\u002Farchitecture-and-quality.md`: architecture, tests,\n  accessibility, performance, and build checks;\n- `references\u002Fprivacy-billing-integrity.md`: privacy, Data Safety, account\n  deletion, Billing, and Integrity controls;\n- `references\u002Fplay-policy-baseline.md`: dated official-policy baseline;\n- `references\u002Fkids-and-family-apps.md`: before building anything whose\n  audience includes children (StoryBeam-style reading apps, beginner lesson\n  apps such as GuitarHub for young players).\n\n## Kids and family apps\n\nWhen the target audience includes children under 13, the Families policy and\nchildren's privacy law shape the architecture, so settle them in the Delivery\nContract, not at listing time:\n\n- Collect no personal data from children: no child accounts, no free-text\n  fields that could capture a name, school, or location, no voice or photo\n  capture, no advertising ID, no precise location.\n- Use only SDKs that are allowed in Families apps, and no ads SDK that is not\n  Families self-certified. No analytics that send persistent identifiers.\n- Keep every story, image, and sound age-appropriate for the declared band,\n  including AI-generated content, with a screening step before display.\n- Put purchases, external links, and settings behind a parental gate.\n\nA conflict with these is an extreme-risk finding under the gate policy.\n\n## Public-Safe Defaults\n\n- Use placeholder IDs such as `com.example.product` until ownership is verified.\n- Keep upload keys, passwords, service-account JSON, API secrets, and production\n  identifiers outside Git; use local\u002FCI secret stores and prove ignore rules.\n- Use Play App Signing and a distinct upload key.\n- Prefer a free v1 when Billing would delay validation, but do not bypass Play\n  Billing for covered digital goods.\n- Collect no data and request no permission without a stated product purpose,\n  retention\u002Fdeletion rule, disclosure path, and test.\n- Treat Play Integrity as an abuse signal, not authentication and not the sole\n  basis for a permanent block.\n- Keep submission and rollout actions human-confirmed and reversible where the\n  platform permits.\n\n## Release Gate\n\nCopy `assets\u002Fandroid-release-gate.template.md` into the app repo and complete it\nwith links or command output. Recommend `hold` when any required item lacks\nevidence, including:\n\n- target policy was not checked live or the build targets the wrong API\u002Fform\n  factor;\n- a release targeting Android 15+ has not been verified for 16 KB page-size\n  compatibility on 64-bit devices, including transitive native SDKs;\n- `test`, lint\u002Fstatic analysis, `assembleRelease`, or `bundleRelease` fails;\n- the core loop fails on the declared device\u002FAPI matrix or offline\u002Ferror path;\n- accessibility checks, large text, TalkBack, keyboard\u002Fswitch access, contrast,\n  or reduced-motion behavior have launch-critical failures;\n- performance evidence is missing for startup or the core task, or a known\n  regression exceeds the product budget without approval;\n- Data Safety, privacy policy, permissions, account deletion, content rating,\n  ads, app access, or SDK behavior disagree;\n- Billing runs on a Billing Library version Play no longer accepts, or\n  entitlement, pending, restore\u002Frequery, acknowledgement, cancellation,\n  refund\u002Frevocation, or backend verification behavior is unproven when relevant;\n- a child-directed app collects personal data, ships a non-Families ads SDK, or\n  shows content outside its declared age band;\n- secrets or signing material are committed, or Play App Signing\u002Fupload-key\n  ownership, developer verification, or package registration is unresolved;\n- listing claims or screenshots show behavior not present in the release build;\n- a Play upload, track promotion, or rollout lacks explicit user confirmation.\n\nReturn one gate: `ship`, `ship-with-caveats`, or `hold`. A caveat must have an\nowner, risk, and next action; policy, security, privacy, billing, crash, and\ncore-task blockers cannot be downgraded to cosmetic caveats.\n\n## Routing\n\n- Existing-app findings-only review → `suede-code --findings-only`.\n- CI implementation around the release evidence → `suede-ci-gate`.\n- Coordinated architecture, product, policy, store, and QA lanes →\n  `suede-agent-teams` with exclusive file ownership and a serialized release\n  lane.\n- Play upload, track promotion, staged rollout, live-state readback →\n  `suede-play-release`.\n- Play listing, keywords, screenshots, ratings → `suede-aso`.\n- Same product from an existing website on iOS → `site-to-ios-app`. A native\n  iOS build with no website is a private Suede AI companion, not in this pack.\n\n## Boundaries\n\n- Do not submit, create products, change pricing, promote tracks, or start a\n  production rollout without explicit confirmation.\n- Do not answer Play policy or Data Safety questions from memory when live\n  official guidance or the Play Console is available.\n- Do not claim release-ready from a debug build, screenshot, local source\n  inspection, or successful upload alone.\n- Do not use Play Integrity as a substitute for server authorization, purchase\n  verification, rate limits, fraud operations, or an appeal path.\n- Do not call a Data Safety form complete until first-party code and every\n  included SDK have been inventoried against actual release behavior.\n- When a confirmation gate fires (product creation, credential use, upload,\n  track promotion, rollout, production release), halt: name the exact package\n  ID, track, and rollout percentage, offer 2-4 options, and wait. Irreversible\n  public action is the gate policy's single exception; the user's choice is final.\n",{"name":5,"metadata":46,"description":7},{"display-name":47},"Suede AI Android App Factory Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-app-factory",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-app-factory",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill android-app-factory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002FSKILL.md",true,[72,78,84,88,92,96,100,104,108],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",819,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Fagents\u002Fopenai.yaml",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fandroid-release-gate.template.md","ASSET","资产文件",5081,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Fassets\u002Fandroid-release-gate.template.md",{"path":85,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":86,"sourceHtmlUrl":87},"CARD.md",4866,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002FCARD.md",{"path":89,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fandroid-factory-pipeline.md",8791,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Fandroid-factory-pipeline.md",{"path":93,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Farchitecture-and-quality.md",8179,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Farchitecture-and-quality.md",{"path":97,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fkids-and-family-apps.md",3112,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Fkids-and-family-apps.md",{"path":101,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fplay-policy-baseline.md",8128,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Fplay-policy-baseline.md",{"path":105,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fprivacy-billing-integrity.md",7302,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Fprivacy-billing-integrity.md",{"path":109,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fworked-contract.md",2223,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fandroid-app-factory\u002Freferences\u002Fworked-contract.md",[113,123,131,139,147,155],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":122},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":122},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":122},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":122},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":122},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":122},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]