[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RY33VMYR5YNPVFKWRNW9S":3,"skill-same:01M79RY33VMYR5YNPVFKWRNW9S":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79RY33VMYR5YNPVFKWRNW9S","tk-studio-playable-judge",null,"The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says \"judge the playable frames\".","thkennedy\u002Ftk-studio","thkennedy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4164502?v=4","01M79QZ8DMP5FF2HC6GS3S6FDF","Tim Kennedy","01M79QZ8EM9JBWJ15R5JNC4PW3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tk-studio-playable-judge\ndescription: The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says \"judge the playable frames\".\n---\n\n# tk-studio-playable-judge\n\nThe host leg's third step (after a green engine gate) runs `playable.py run`\non the host and copies its media into the worktree's ignored\n`.bmad-loop\u002Fruns\u002F\u003Cengine>\u002Fplayable\u002F`. This session judges those frames. It is\na screenshot judge, nothing more.\n\n## What it may read\n\n- **Only** `report.json` and the frames (`frames\u002F*.png`) under the payload's\n  `media` folder (relative to the payload `directory`).\n- **Never** the project's code, scenes, scripts, the spec, the story, the\n  plan or any other file. Do not list, grep or open anything outside `media`.\n  A judge that read the code would grade intent, not what the game showed.\n\n## Behavior (headless)\n\n1. Prepare through the deterministic core (it validates the report and the\n   frames, and prints the frame list, the moments and the rubric):\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fplayable_judge.py\" prepare --media \"\u003Cdirectory>\u002F\u003Cmedia>\"\n   ```\n\n   A `blocked` result (`no report.json`, `malformed report: \u003Cfield>`,\n   `no frames`) ends the run `blocked` with that reason.\n\n2. Look at every frame the core listed (`Read` on each PNG) and answer each\n   rubric line by its fixed id:\n\n   | id | rubric line |\n   |----|-------------|\n   | `scene-loaded` | the scene loaded |\n   | `player-visible` | the player is visible and framed |\n   | `no-magenta-or-error-overlay` | no missing-texture magenta and no error overlay |\n   | `hud-reads` | the HUD reads |\n   | `moments-shown` | the scenario's named moments appear in the frames they name |\n\n3. Write the answer to a file under `media` (`answer.json`):\n\n   ```json\n   {\"verdict\": \"fail\", \"findings\": [{\"frame\": \"frames\u002Ftick-000030.png\", \"rubric\": \"hud-reads\", \"note\": \"the HUD is clipped off the right edge\"}]}\n   ```\n\n   `verdict` is `pass` or `fail`. Every finding names one frame from the\n   core's list and one rubric id, with a one-line note. A `fail` carries at\n   least one finding. A `pass` may carry none.\n\n4. Record the verdict through the core (it writes `\u003Cmedia>\u002Fjudge.json`, the\n   file the host leg reads back):\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fplayable_judge.py\" verdict --media \"\u003Cdirectory>\u002F\u003Cmedia>\" --answer \"\u003Cdirectory>\u002F\u003Cmedia>\u002Fanswer.json\"\n   ```\n\n   A refusal (`unknown rubric id`, `frame not in frames[]`, `fail with no\n   findings`, `malformed answer`) may be corrected once by rewriting the\n   answer; a second refusal ends the run `blocked` with that reason.\n\n5. End with the status block (the verdict lives in `judge.json`, never in\n   the block; a judged `fail` is still a `complete` run):\n\n   ```json\n   {\"status\": \"complete\", \"intent\": \"tk-studio-playable-judge\", \"artifacts\": [\"judge.json\"], \"reason\": null}\n   ```\n\nIf the deterministic core is unrunnable — a tool call denied by permissions, `uv`\u002Fpython unavailable — end `blocked` with the status block naming the unrunnable core as `reason`: never a question, never a headless run that ends without the block (AD-11).\n\n## Rules\n\n- Never prompt or ask: everything arrives in the payload (`media`,\n  `directory`); a missing `media` is a `blocked` status (AD-11).\n- Never edit the frames, `report.json` or anything outside `media`; the only\n  files this session writes are `answer.json` and (through the core)\n  `judge.json`.\n- All plugin paths resolve through `${CLAUDE_PLUGIN_ROOT}`.\n","# tk-studio-playable-judge\n\nThe host leg's third step (after a green engine gate) runs `playable.py run`\non the host and copies its media into the worktree's ignored\n`.bmad-loop\u002Fruns\u002F\u003Cengine>\u002Fplayable\u002F`. This session judges those frames. It is\na screenshot judge, nothing more.\n\n## What it may read\n\n- **Only** `report.json` and the frames (`frames\u002F*.png`) under the payload's\n  `media` folder (relative to the payload `directory`).\n- **Never** the project's code, scenes, scripts, the spec, the story, the\n  plan or any other file. Do not list, grep or open anything outside `media`.\n  A judge that read the code would grade intent, not what the game showed.\n\n## Behavior (headless)\n\n1. Prepare through the deterministic core (it validates the report and the\n   frames, and prints the frame list, the moments and the rubric):\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fplayable_judge.py\" prepare --media \"\u003Cdirectory>\u002F\u003Cmedia>\"\n   ```\n\n   A `blocked` result (`no report.json`, `malformed report: \u003Cfield>`,\n   `no frames`) ends the run `blocked` with that reason.\n\n2. Look at every frame the core listed (`Read` on each PNG) and answer each\n   rubric line by its fixed id:\n\n   | id | rubric line |\n   |----|-------------|\n   | `scene-loaded` | the scene loaded |\n   | `player-visible` | the player is visible and framed |\n   | `no-magenta-or-error-overlay` | no missing-texture magenta and no error overlay |\n   | `hud-reads` | the HUD reads |\n   | `moments-shown` | the scenario's named moments appear in the frames they name |\n\n3. Write the answer to a file under `media` (`answer.json`):\n\n   ```json\n   {\"verdict\": \"fail\", \"findings\": [{\"frame\": \"frames\u002Ftick-000030.png\", \"rubric\": \"hud-reads\", \"note\": \"the HUD is clipped off the right edge\"}]}\n   ```\n\n   `verdict` is `pass` or `fail`. Every finding names one frame from the\n   core's list and one rubric id, with a one-line note. A `fail` carries at\n   least one finding. A `pass` may carry none.\n\n4. Record the verdict through the core (it writes `\u003Cmedia>\u002Fjudge.json`, the\n   file the host leg reads back):\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fplayable_judge.py\" verdict --media \"\u003Cdirectory>\u002F\u003Cmedia>\" --answer \"\u003Cdirectory>\u002F\u003Cmedia>\u002Fanswer.json\"\n   ```\n\n   A refusal (`unknown rubric id`, `frame not in frames[]`, `fail with no\n   findings`, `malformed answer`) may be corrected once by rewriting the\n   answer; a second refusal ends the run `blocked` with that reason.\n\n5. End with the status block (the verdict lives in `judge.json`, never in\n   the block; a judged `fail` is still a `complete` run):\n\n   ```json\n   {\"status\": \"complete\", \"intent\": \"tk-studio-playable-judge\", \"artifacts\": [\"judge.json\"], \"reason\": null}\n   ```\n\nIf the deterministic core is unrunnable — a tool call denied by permissions, `uv`\u002Fpython unavailable — end `blocked` with the status block naming the unrunnable core as `reason`: never a question, never a headless run that ends without the block (AD-11).\n\n## Rules\n\n- Never prompt or ask: everything arrives in the payload (`media`,\n  `directory`); a missing `media` is a `blocked` status (AD-11).\n- Never edit the frames, `report.json` or anything outside `media`; the only\n  files this session writes are `answer.json` and (through the core)\n  `judge.json`.\n- All plugin paths resolve through `${CLAUDE_PLUGIN_ROOT}`.\n",{"name":5,"description":7},"main","ecd23b3c0458cd511812f643d9111e3d7c8235f4","plugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio","https:\u002F\u002Fgithub.com\u002Fthkennedy","https:\u002F\u002Ftimothyhkennedy.com","Just a guy who loves making tools, automation and games.","2026-11-10 20:38:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add thkennedy\u002Ftk-studio --skill tk-studio-playable-judge",{"tool":38,"command":39},"bunx","bunx skills add thkennedy\u002Ftk-studio --skill tk-studio-playable-judge",{"tool":41,"command":42},"pnpm","pnpm dlx skills add thkennedy\u002Ftk-studio --skill tk-studio-playable-judge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"customize.toml","OTHER","其他",581,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002Fcustomize.toml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79RYSQ8C3MWDFTDSRAYFJYA","tk-studio-track","Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to \"Blocked - Awaiting User\" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to \"Done\"); `reply` posts the owner's answer (or \"Done.\") with the owner's host-only token and moves the issue to \"Block Resolved\"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says \"block this story\", \"tk track block\", \"put it in the owner's inbox\", \"reply to the blocked issue\", \"validate the resolution\", or a supervisor or engagement payload names this skill.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-track\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79RYMVE0031EV5B64MBGD8V","tk-studio-session","Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says \"hand off this run\", \"tk session\", \"resume the run\", or a boundary\u002Fbudget trigger says the session must split.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-session\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79RYFM9ATWHM6HAXJ3D19WV","tk-studio-research","Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says \"run the ecosystem watch\", \"tk research\", or a research job's invoke-skill directive names this skill.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-research\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79RYA1AWZZF83KBHGR6JDN3","tk-studio-report","One-verb human defect report — \"the skill did the wrong thing\" — recorded as a report event in the local measurement ledger. Use when the user says \"tk report\", \"report a defect\", \"that skill misbehaved\", or \"log a studio issue\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-report\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79RXY4AM8JM6ZK2MAR3W3X2","tk-studio-plan-sync","Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says \"sync the plan\", \"normalize planning artifacts\", \"tk plan sync\", or after stock BMad planning flows produce or change epics\u002Fstories.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-plan-sync\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79RXRDV34SQ7160973XEZ1A","tk-studio-orchestrator","The studio's front door — resolve who you are (role, per-user store), what this project needs (confirmed working_set.\u003Crole>), and route to resources by name, statelessly. Use when the user says \"enter the studio\", \"tk studio\", \"orchestrate\", \"convene the council\", or asks what to work on through the studio.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-orchestrator\u002FSKILL.md",[],[]]