[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSG68E10FTJC0H15N9RSFJ":3,"skill-same:01M7CSG68E10FTJC0H15N9RSFJ":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSG68E10FTJC0H15N9RSFJ","batch-artifact-verification",null,"Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fbatch-artifact-verification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: batch-artifact-verification\ncategory: release\ndescription: Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag\nsource: olivierlacan\u002Fkeep-a-changelog (MIT), adapted\n---\n\n# Batch artifact verification\n\nA batch release (desktop, mobile and other human-cut components) has no bound runtime environment — see `post-deploy-verification`'s last section. Its evidence is whether the thing it built actually got published and is what users will fetch next, per executor.\n\n## `github_actions` \u002F `local`\n\n```\nrun_terminal(\"gh release view \u003Ctag> --json tagName,isDraft,isPrerelease,isImmutable,publishedAt,assets\")\n```\n\nExpect `isDraft: false`, the platform's assets present with `size > 0`, and the update-feed file if the app ships one (e.g. `latest-mac.yml`). If `gh` is unavailable but the repository is public, fall back to `fetch_url https:\u002F\u002Fapi.github.com\u002Frepos\u002F\u003Cowner>\u002F\u003Crepo>\u002Freleases\u002Ftags\u002F\u003Ctag>`.\n\nIf the repository brief names an update feed or a Homebrew cask URL, `fetch_url` it and confirm it names the new version — that is what actually reaches an existing install, not the GitHub Release page by itself.\n\nFor a `local` executor, the exit code is the first signal: `local_run.exit_code == 0`, with `local_run.tail` showing the publish step actually ran (not just that the build compiled).\n\n## `store`\n\nEvery entry in `store_builds[]` must have `build != baseline_build` and carry no `error`. A `baseline_build` of `\"?\"` means the baseline was never confirmed — say so rather than treating it as a pass. \"Deployed\" here means the build reached the internal\u002Ftesting channel; promoting it to production is a human step taken in the store console, and your finish note says so explicitly rather than implying the rollout is live.\n\n## Yanking a bad batch release\n\nThis is the first `manual_steps` item on a batch rollback (`rollback-runbook`), and you perform it yourself — it is the one write `release-terminal-scope` allows:\n\n```\nrun_terminal('gh release edit \u003Ctag> --prerelease --title \"\u003Cname> [YANKED]\"')\n```\n\nThis works on an immutable release (title, notes and prerelease\u002Flatest stay editable; assets and the tag itself do not) and removes it from GitHub's \"latest\" resolution (the most recent non-prerelease, non-draft release), which most update feeds follow via `\u002Freleases\u002Flatest`. Then point \"latest\" back at the previous good release:\n\n```\nrun_terminal(\"gh release edit \u003Cprevious-good-tag> --latest\")\n```\n\nRecord the exact commands you ran and their output as evidence on the card — this is not a suggestion for a human to carry out, it is work you did and are reporting.\n\nNever delete the release or its tag, and never `git push --delete` it — an immutable tag cannot be reused (GitHub Docs: immutable releases), and SemVer §3 holds here too: a released version's contents are never modified, only marked bad. A cask\u002Fupdate-feed PR pointing at the new tag, or halting a store rollout, are human steps outside `gh release`'s reach — report them, naming exactly what needs to change and where.\n\n✅ \"Yanked v2.4.1: `gh release edit v2.4.1 --prerelease --title \\\"TaskTrooper 2.4.1 [YANKED]\\\"` (exit 0); restored latest to v2.4.0: `gh release edit v2.4.0 --latest` (exit 0). `gh release view v2.4.1` now shows `isPrerelease: true`. Left for a human: the Homebrew cask formula still points at v2.4.1 — needs a PR bumping it back to v2.4.0.\"\n\n❌ \"Release looks bad, someone should pull it.\" — no command run, no evidence, and it was this agent's job to run it, not a human's.\n\n## Common Mistakes\n\n- Treating a store build reaching the internal channel as \"released to users\" — it is not, until a human promotes it.\n- Deleting a release or tag instead of marking it `[YANKED]` and moving `--latest`.\n- Reporting a yank as done without the command output that proves it happened.\n- Checking only `isDraft`\u002F`isPrerelease` and skipping the update feed — a feed that still points at the bad tag means existing installs keep fetching it even after the GitHub Release itself is marked yanked.\n","# Batch artifact verification\n\nA batch release (desktop, mobile and other human-cut components) has no bound runtime environment — see `post-deploy-verification`'s last section. Its evidence is whether the thing it built actually got published and is what users will fetch next, per executor.\n\n## `github_actions` \u002F `local`\n\n```\nrun_terminal(\"gh release view \u003Ctag> --json tagName,isDraft,isPrerelease,isImmutable,publishedAt,assets\")\n```\n\nExpect `isDraft: false`, the platform's assets present with `size > 0`, and the update-feed file if the app ships one (e.g. `latest-mac.yml`). If `gh` is unavailable but the repository is public, fall back to `fetch_url https:\u002F\u002Fapi.github.com\u002Frepos\u002F\u003Cowner>\u002F\u003Crepo>\u002Freleases\u002Ftags\u002F\u003Ctag>`.\n\nIf the repository brief names an update feed or a Homebrew cask URL, `fetch_url` it and confirm it names the new version — that is what actually reaches an existing install, not the GitHub Release page by itself.\n\nFor a `local` executor, the exit code is the first signal: `local_run.exit_code == 0`, with `local_run.tail` showing the publish step actually ran (not just that the build compiled).\n\n## `store`\n\nEvery entry in `store_builds[]` must have `build != baseline_build` and carry no `error`. A `baseline_build` of `\"?\"` means the baseline was never confirmed — say so rather than treating it as a pass. \"Deployed\" here means the build reached the internal\u002Ftesting channel; promoting it to production is a human step taken in the store console, and your finish note says so explicitly rather than implying the rollout is live.\n\n## Yanking a bad batch release\n\nThis is the first `manual_steps` item on a batch rollback (`rollback-runbook`), and you perform it yourself — it is the one write `release-terminal-scope` allows:\n\n```\nrun_terminal('gh release edit \u003Ctag> --prerelease --title \"\u003Cname> [YANKED]\"')\n```\n\nThis works on an immutable release (title, notes and prerelease\u002Flatest stay editable; assets and the tag itself do not) and removes it from GitHub's \"latest\" resolution (the most recent non-prerelease, non-draft release), which most update feeds follow via `\u002Freleases\u002Flatest`. Then point \"latest\" back at the previous good release:\n\n```\nrun_terminal(\"gh release edit \u003Cprevious-good-tag> --latest\")\n```\n\nRecord the exact commands you ran and their output as evidence on the card — this is not a suggestion for a human to carry out, it is work you did and are reporting.\n\nNever delete the release or its tag, and never `git push --delete` it — an immutable tag cannot be reused (GitHub Docs: immutable releases), and SemVer §3 holds here too: a released version's contents are never modified, only marked bad. A cask\u002Fupdate-feed PR pointing at the new tag, or halting a store rollout, are human steps outside `gh release`'s reach — report them, naming exactly what needs to change and where.\n\n✅ \"Yanked v2.4.1: `gh release edit v2.4.1 --prerelease --title \\\"TaskTrooper 2.4.1 [YANKED]\\\"` (exit 0); restored latest to v2.4.0: `gh release edit v2.4.0 --latest` (exit 0). `gh release view v2.4.1` now shows `isPrerelease: true`. Left for a human: the Homebrew cask formula still points at v2.4.1 — needs a PR bumping it back to v2.4.0.\"\n\n❌ \"Release looks bad, someone should pull it.\" — no command run, no evidence, and it was this agent's job to run it, not a human's.\n\n## Common Mistakes\n\n- Treating a store build reaching the internal channel as \"released to users\" — it is not, until a human promotes it.\n- Deleting a release or tag instead of marking it `[YANKED]` and moving `--latest`.\n- Reporting a yank as done without the command output that proves it happened.\n- Checking only `isDraft`\u002F`isPrerelease` and skipping the update feed — a feed that still points at the bad tag means existing installs keep fetching it even after the GitHub Release itself is marked yanked.\n",{"name":5,"source":24,"category":25,"description":7},"olivierlacan\u002Fkeep-a-changelog (MIT), adapted","release","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fbatch-artifact-verification",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill batch-artifact-verification",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill batch-artifact-verification",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill batch-artifact-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fbatch-artifact-verification\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]