[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9BEWHHTJY3GRJ39GE6ZSY":3,"skill-same:01M6M9BEWHHTJY3GRJ39GE6ZSY":97},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6M9BEWHHTJY3GRJ39GE6ZSY","suede-play-release",null,"Suede AI Google Play Release Skills. Google Play release delivery with AAB preflight, test-track upload, exact versionCode promotion, staged rollout, locale notes, and API readback. Use when asked \"promote this Android build\" or to diagnose Play publishing access and prove the served release. NOT FOR: app building or policy review (android-app-factory), listing assets (suede-aso), or CI gates (suede-ci-gate).","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\u002Fsuede-play-release\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"suede play release","release","play","aso","listing","when","android build","track","locale","release skills","app","delivery","rollout","google","access","preflight","api","ci","promote","notes","diagnose","review","2026-11-10 10:12:30",false,"---\nname: suede-play-release\ndescription: \"Suede AI Google Play Release Skills. Google Play release delivery with AAB preflight, test-track upload, exact versionCode promotion, staged rollout, locale notes, and API readback. Use when asked \\\"promote this Android build\\\" or to diagnose Play publishing access and prove the served release. NOT FOR: app building or policy review (android-app-factory), listing assets (suede-aso), or CI gates (suede-ci-gate).\"\nmetadata:\n  display-name: \"Suede AI Google Play Release Skills\"\n---\n\n# Suede AI Google Play Release Skills\n\n## Compatibility\n\nRequires Android release artifacts and authorized Google Play publishing access. Bundled preflight uses Python with pyjwt\u002Fcryptography and macOS Keychain; delivery examples use fastlane supply. Linux CI uses its secret store.\n\nUse [the worked contract](references\u002Fworked-contract.md) for a staged rollout\nexample, access-failure recovery, and API readback validation.\n\n```text\nIron Law: the Play API decides what shipped, not a green fastlane summary.\nEvery claim about a live release is a readback or it is a guess.\n```\n\n## Gate policy: advisory, not blocking\n\nRun every check and report results honestly. Verdicts are advice attached to the\nwork, never a control that changes it. A failed check changes what you report,\nnever what you do. The one exception is the production halt in Step 7: a public\nrelease is irreversible for the users who get it, so present the options and let\nthe user pick.\n\n## Step 0: Preflight the credential before anything else\n\nNever assume publishing works. Prove it with a real API call that changes\nnothing: open an edit and delete it. The script reads the key from the macOS\nlogin Keychain and needs `pyjwt` and `cryptography`; on Linux CI, load the same\nbase64 JSON from the CI secret store and run the equivalent token exchange.\n\n```bash\npython3 scripts\u002Fplay-preflight.py \u003Cpackage.name> [--service NAME] [--account NAME]\n```\n\nThree outcomes, three different actions:\n\n| Result | Meaning | Do |\n| --- | --- | --- |\n| token fails | key is wrong or revoked | rotate, see Step 1 |\n| HTTP 401\u002F403 on the edit | Play Console has not granted the account | Step 1's grant |\n| edit opens and deletes | publishing is wired | continue |\n\nA 403 here is the normal state of a brand-new service account, not a bug.\n\n## Step 1: Credentials\n\nUse a **dedicated publishing service account**, separate from any billing or\npurchase-verification account. A credential that can push releases should not\nalso be able to void purchases. Give it no cloud IAM roles: all of its authority\ncomes from the Play Console grant, so before that grant the key is inert.\n\nStore the JSON in the login Keychain **base64-encoded**:\n\n```bash\nsecurity add-generic-password -U -s GOOGLE_PLAY_SERVICE_ACCOUNT_JSON -a \u003Caccount> -w\n```\n\nRun it with `-w` last and no value so it prompts and the key never enters shell\nhistory. Paste the base64, not the raw JSON.\n\nBase64 is load-bearing. `security` hex-encodes any multi-line secret on read, so\nraw JSON comes back in one of two shapes depending on content. Base64 gives one\nshape and one decode path.\n\nGranting access is a **Play Console UI action** and cannot be done from the API:\ninvite the service-account email under Users and permissions with release\npermissions on the app. Report this to the user as a step only they can take,\nwith the exact email and permissions, then re-run Step 0.\n\n## Step 2: Pull before every command\n\n`fastlane` reads the working tree, not the remote. A stale checkout produces a\nrun that succeeds and does nothing, because a missing changelog is a skip rather\nthan an error.\n\n```bash\ngit -C \u003Crepo> pull --ff-only && git -C \u003Crepo> log --oneline -1\n```\n\nIf fastlane offers to set itself up, the Fastfile is not on disk. Answer no and\npull; accepting scaffolds an empty config over the real one.\n\n## Step 3: Write the changelog first\n\nRelease notes live at\n`fastlane\u002Fmetadata\u002Fandroid\u002F\u003Clocale>\u002Fchangelogs\u002F\u003CversionCode>.txt`, one file per\nlocale per versionCode.\n\nA missing file is **not** an error. Play silently serves the previous version's\nnotes, so users read stale text against a new build and nothing tells you. Write\none for every locale that has listing copy, before uploading.\n\n```bash\nfor l in $(ls fastlane\u002Fmetadata\u002Fandroid); do\n  [ -f \"fastlane\u002Fmetadata\u002Fandroid\u002F$l\u002Fchangelogs\u002F$VC.txt\" ] || echo \"MISSING: $l\"\ndone\n```\n\nMatch each locale's existing register rather than translating the English word\nfor word. Check the limit: 500 characters.\n\n## Step 4: Verify the artifact, never the source tree\n\nA source read is not evidence that a change reached the binary.\n\n```bash\njarsigner -verify app\u002Fbuild\u002Foutputs\u002Fbundle\u002Frelease\u002Fapp-release.aab | head -1\ngrep -oE 'android:version(Code|Name)=\"[^\"]*\"' \\\n  app\u002Fbuild\u002Fintermediates\u002Fmerged_manifests\u002Frelease\u002F*\u002FAndroidManifest.xml\n```\n\nWhen the release changes an asset, hash it on both sides and require a match:\n\n```bash\nunzip -p \u003Caab> 'base\u002Fres\u002F*xxxhdpi*ic_launcher.png' | shasum -a 256\nshasum -a 256 app\u002Fsrc\u002Fmain\u002Fres\u002Fmipmap-xxxhdpi\u002Fic_launcher.png\n```\n\n`jarsigner` reporting a self-signed certificate is correct under Play App\nSigning, which re-signs with the real release key.\n\n## Step 5: Upload to a testing track first\n\n```bash\nfastlane android internal\n```\n\nBuild uploads carry the binary and its changelogs only. Listing text, icon,\nfeature graphic and screenshots move through a separate lane, so a routine\nupload cannot rewrite what the store says about the app.\n\n## Step 6: Promote, never re-upload\n\nPlay rejects a second bundle carrying a versionCode it already has. Re-uploading\nis not a slower path to the same place, it is an error.\n\nPromote the versionCode already on the testing track, which is also the only\nthing that makes testing-first mean anything: the artifact reaching production is\nthe one that was validated, bit for bit.\n\n```ruby\nupload_to_play_store(\n  version_code: \u003Ccode>, track: \"internal\", track_promote_to: \"production\",\n  skip_upload_aab: true, skip_upload_apk: true,\n  release_status: \"inProgress\", rollout: \"0.1\"\n)\n```\n\n## Step 7: Production halt\n\nA production rollout is irreversible for the users who receive it. Stop and\npresent:\n\n```text\nReady to promote versionCode \u003Cn> (\u003Cname>) to production at \u003Cpct>% of users.\nCurrently live: versionCode \u003Cm>. \u003Cone line on what users will notice>.\n  1. Promote at \u003Cpct>%\n  2. Promote at a different fraction\n  3. Upload to a testing track only\n  4. Hold\n```\n\nThen wait. Proceed on an explicit answer, and treat a standing instruction to\nship as that answer.\n\n## Step 8: Read back what is actually live\n\nThe fastlane summary reports that the request succeeded, not what the release\nbecame. Parameters like `track_promote_release_status` can differ from the\n`release_status` you set, so read the track:\n\n```\nGET \u002Fandroidpublisher\u002Fv3\u002Fapplications\u002F\u003Cpkg>\u002Fedits\u002F\u003Cid>\u002Ftracks\u002Fproduction\n```\n\nCheck three fields and say them plainly:\n\n- `versionCodes`: the build users get.\n- `status`: `inProgress` is a staged rollout; `completed` is everyone.\n- `userFraction`: absent when `completed`.\n\nA 100% rollout should land as `status: completed` with **no** `userFraction`. A\nrelease sitting at `inProgress` with `userFraction: 1.0` is a different state\nthat reads the same in a success message. Confirm which one you got.\n\nAlso confirm every locale you wrote appears in that release's `releaseNotes`.\n\n## Done means\n\nEvery line proven by a command in this run:\n\n- Preflight opened and deleted a real Play edit.\n- The AAB verified: signature, versionCode in the merged manifest, and a hash\n  match for any changed asset.\n- The track readback shows the expected versionCode, status, and fraction.\n- Every locale with listing copy appears in the live release's notes.\n\n## Boundaries\n\n1. Do not promote to production, raise a rollout, or halt one without an\n   explicit instruction covering that action.\n2. Do not create the Play Console grant yourself; it is a UI action. Name the\n   email and permissions and hand it to the user.\n3. Do not print, commit, or copy the service-account JSON, the upload keystore,\n   or `keystore.properties` into a repo.\n4. Do not push listing text, images, or screenshots as part of a build upload.\n   Store copy moves in its own deliberate step.\n5. Do not report a release state from a fastlane summary. Read the track.\n6. Do not reuse a billing or purchase-verification service account for\n   publishing.\n7. Do not edit a changelog for a versionCode already serving users to fix a\n   typo silently; that changes live store copy and belongs in the same\n   confirmation as a rollout change.\n\n## Routing\n\n- Need to plan, build, test, or policy-check the app itself -> use\n  `android-app-factory`, then return here for delivery.\n- Need listing text, keywords, screenshots, or ratings work -> use\n  `suede-aso`. Listing changes travel in their own deliberate step (Boundary 4),\n  so plan them there and ship them separately from the binary.\n- Need CI wiring, required checks, or merge gates around the release -> use\n  `suede-ci-gate`.\n- Need branch, worktree, or stale-mirror handling for the release branch, or\n  the iOS half of the same release -> private Suede AI companions, not in this\n  pack.\n- Need constants to match across the Android, iOS and web surfaces -> use\n  `suede-parity-contract`.\n- From `android-app-factory`: route Play credential setup, upload,\n  track promotion, staged rollout, and live-state verification back here.\n","# Suede AI Google Play Release Skills\n\n## Compatibility\n\nRequires Android release artifacts and authorized Google Play publishing access. Bundled preflight uses Python with pyjwt\u002Fcryptography and macOS Keychain; delivery examples use fastlane supply. Linux CI uses its secret store.\n\nUse [the worked contract](references\u002Fworked-contract.md) for a staged rollout\nexample, access-failure recovery, and API readback validation.\n\n```text\nIron Law: the Play API decides what shipped, not a green fastlane summary.\nEvery claim about a live release is a readback or it is a guess.\n```\n\n## Gate policy: advisory, not blocking\n\nRun every check and report results honestly. Verdicts are advice attached to the\nwork, never a control that changes it. A failed check changes what you report,\nnever what you do. The one exception is the production halt in Step 7: a public\nrelease is irreversible for the users who get it, so present the options and let\nthe user pick.\n\n## Step 0: Preflight the credential before anything else\n\nNever assume publishing works. Prove it with a real API call that changes\nnothing: open an edit and delete it. The script reads the key from the macOS\nlogin Keychain and needs `pyjwt` and `cryptography`; on Linux CI, load the same\nbase64 JSON from the CI secret store and run the equivalent token exchange.\n\n```bash\npython3 scripts\u002Fplay-preflight.py \u003Cpackage.name> [--service NAME] [--account NAME]\n```\n\nThree outcomes, three different actions:\n\n| Result | Meaning | Do |\n| --- | --- | --- |\n| token fails | key is wrong or revoked | rotate, see Step 1 |\n| HTTP 401\u002F403 on the edit | Play Console has not granted the account | Step 1's grant |\n| edit opens and deletes | publishing is wired | continue |\n\nA 403 here is the normal state of a brand-new service account, not a bug.\n\n## Step 1: Credentials\n\nUse a **dedicated publishing service account**, separate from any billing or\npurchase-verification account. A credential that can push releases should not\nalso be able to void purchases. Give it no cloud IAM roles: all of its authority\ncomes from the Play Console grant, so before that grant the key is inert.\n\nStore the JSON in the login Keychain **base64-encoded**:\n\n```bash\nsecurity add-generic-password -U -s GOOGLE_PLAY_SERVICE_ACCOUNT_JSON -a \u003Caccount> -w\n```\n\nRun it with `-w` last and no value so it prompts and the key never enters shell\nhistory. Paste the base64, not the raw JSON.\n\nBase64 is load-bearing. `security` hex-encodes any multi-line secret on read, so\nraw JSON comes back in one of two shapes depending on content. Base64 gives one\nshape and one decode path.\n\nGranting access is a **Play Console UI action** and cannot be done from the API:\ninvite the service-account email under Users and permissions with release\npermissions on the app. Report this to the user as a step only they can take,\nwith the exact email and permissions, then re-run Step 0.\n\n## Step 2: Pull before every command\n\n`fastlane` reads the working tree, not the remote. A stale checkout produces a\nrun that succeeds and does nothing, because a missing changelog is a skip rather\nthan an error.\n\n```bash\ngit -C \u003Crepo> pull --ff-only && git -C \u003Crepo> log --oneline -1\n```\n\nIf fastlane offers to set itself up, the Fastfile is not on disk. Answer no and\npull; accepting scaffolds an empty config over the real one.\n\n## Step 3: Write the changelog first\n\nRelease notes live at\n`fastlane\u002Fmetadata\u002Fandroid\u002F\u003Clocale>\u002Fchangelogs\u002F\u003CversionCode>.txt`, one file per\nlocale per versionCode.\n\nA missing file is **not** an error. Play silently serves the previous version's\nnotes, so users read stale text against a new build and nothing tells you. Write\none for every locale that has listing copy, before uploading.\n\n```bash\nfor l in $(ls fastlane\u002Fmetadata\u002Fandroid); do\n  [ -f \"fastlane\u002Fmetadata\u002Fandroid\u002F$l\u002Fchangelogs\u002F$VC.txt\" ] || echo \"MISSING: $l\"\ndone\n```\n\nMatch each locale's existing register rather than translating the English word\nfor word. Check the limit: 500 characters.\n\n## Step 4: Verify the artifact, never the source tree\n\nA source read is not evidence that a change reached the binary.\n\n```bash\njarsigner -verify app\u002Fbuild\u002Foutputs\u002Fbundle\u002Frelease\u002Fapp-release.aab | head -1\ngrep -oE 'android:version(Code|Name)=\"[^\"]*\"' \\\n  app\u002Fbuild\u002Fintermediates\u002Fmerged_manifests\u002Frelease\u002F*\u002FAndroidManifest.xml\n```\n\nWhen the release changes an asset, hash it on both sides and require a match:\n\n```bash\nunzip -p \u003Caab> 'base\u002Fres\u002F*xxxhdpi*ic_launcher.png' | shasum -a 256\nshasum -a 256 app\u002Fsrc\u002Fmain\u002Fres\u002Fmipmap-xxxhdpi\u002Fic_launcher.png\n```\n\n`jarsigner` reporting a self-signed certificate is correct under Play App\nSigning, which re-signs with the real release key.\n\n## Step 5: Upload to a testing track first\n\n```bash\nfastlane android internal\n```\n\nBuild uploads carry the binary and its changelogs only. Listing text, icon,\nfeature graphic and screenshots move through a separate lane, so a routine\nupload cannot rewrite what the store says about the app.\n\n## Step 6: Promote, never re-upload\n\nPlay rejects a second bundle carrying a versionCode it already has. Re-uploading\nis not a slower path to the same place, it is an error.\n\nPromote the versionCode already on the testing track, which is also the only\nthing that makes testing-first mean anything: the artifact reaching production is\nthe one that was validated, bit for bit.\n\n```ruby\nupload_to_play_store(\n  version_code: \u003Ccode>, track: \"internal\", track_promote_to: \"production\",\n  skip_upload_aab: true, skip_upload_apk: true,\n  release_status: \"inProgress\", rollout: \"0.1\"\n)\n```\n\n## Step 7: Production halt\n\nA production rollout is irreversible for the users who receive it. Stop and\npresent:\n\n```text\nReady to promote versionCode \u003Cn> (\u003Cname>) to production at \u003Cpct>% of users.\nCurrently live: versionCode \u003Cm>. \u003Cone line on what users will notice>.\n  1. Promote at \u003Cpct>%\n  2. Promote at a different fraction\n  3. Upload to a testing track only\n  4. Hold\n```\n\nThen wait. Proceed on an explicit answer, and treat a standing instruction to\nship as that answer.\n\n## Step 8: Read back what is actually live\n\nThe fastlane summary reports that the request succeeded, not what the release\nbecame. Parameters like `track_promote_release_status` can differ from the\n`release_status` you set, so read the track:\n\n```\nGET \u002Fandroidpublisher\u002Fv3\u002Fapplications\u002F\u003Cpkg>\u002Fedits\u002F\u003Cid>\u002Ftracks\u002Fproduction\n```\n\nCheck three fields and say them plainly:\n\n- `versionCodes`: the build users get.\n- `status`: `inProgress` is a staged rollout; `completed` is everyone.\n- `userFraction`: absent when `completed`.\n\nA 100% rollout should land as `status: completed` with **no** `userFraction`. A\nrelease sitting at `inProgress` with `userFraction: 1.0` is a different state\nthat reads the same in a success message. Confirm which one you got.\n\nAlso confirm every locale you wrote appears in that release's `releaseNotes`.\n\n## Done means\n\nEvery line proven by a command in this run:\n\n- Preflight opened and deleted a real Play edit.\n- The AAB verified: signature, versionCode in the merged manifest, and a hash\n  match for any changed asset.\n- The track readback shows the expected versionCode, status, and fraction.\n- Every locale with listing copy appears in the live release's notes.\n\n## Boundaries\n\n1. Do not promote to production, raise a rollout, or halt one without an\n   explicit instruction covering that action.\n2. Do not create the Play Console grant yourself; it is a UI action. Name the\n   email and permissions and hand it to the user.\n3. Do not print, commit, or copy the service-account JSON, the upload keystore,\n   or `keystore.properties` into a repo.\n4. Do not push listing text, images, or screenshots as part of a build upload.\n   Store copy moves in its own deliberate step.\n5. Do not report a release state from a fastlane summary. Read the track.\n6. Do not reuse a billing or purchase-verification service account for\n   publishing.\n7. Do not edit a changelog for a versionCode already serving users to fix a\n   typo silently; that changes live store copy and belongs in the same\n   confirmation as a rollout change.\n\n## Routing\n\n- Need to plan, build, test, or policy-check the app itself -> use\n  `android-app-factory`, then return here for delivery.\n- Need listing text, keywords, screenshots, or ratings work -> use\n  `suede-aso`. Listing changes travel in their own deliberate step (Boundary 4),\n  so plan them there and ship them separately from the binary.\n- Need CI wiring, required checks, or merge gates around the release -> use\n  `suede-ci-gate`.\n- Need branch, worktree, or stale-mirror handling for the release branch, or\n  the iOS half of the same release -> private Suede AI companions, not in this\n  pack.\n- Need constants to match across the Android, iOS and web surfaces -> use\n  `suede-parity-contract`.\n- From `android-app-factory`: route Play credential setup, upload,\n  track promotion, staged rollout, and live-state verification back here.\n",{"name":5,"metadata":51,"description":7},{"display-name":52},"Suede AI Google Play Release Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release",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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-play-release",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-play-release",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-play-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release\u002FSKILL.md",true,[77,83,87,91],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"agents\u002Fopenai.yaml","REFERENCE","参考文档",1185,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release\u002Fagents\u002Fopenai.yaml",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"CARD.md",4602,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release\u002FCARD.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworked-contract.md",2670,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release\u002Freferences\u002Fworked-contract.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fplay-preflight.py","SCRIPT","脚本",4796,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-play-release\u002Fscripts\u002Fplay-preflight.py",[98,108,116,124,132,140],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":107},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":107},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":107},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":107},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":107},"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",[],[]]