[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RWDMHAQQJXDKS7B8KHWD0":3,"skill-same:01M79RWDMHAQQJXDKS7B8KHWD0":58},{"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},"01M79RWDMHAQQJXDKS7B8KHWD0","tk-studio-install",null,"Install the BMad base at the committed bmad.lock pin with the project's module set — non-interactive, deterministic, zero forks. Use when the user says \"tk install\", \"install the base\", or \"install bmad at the pin\".","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-install\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tk-studio-install\ndescription: Install the BMad base at the committed bmad.lock pin with the project's module set — non-interactive, deterministic, zero forks. Use when the user says \"tk install\", \"install the base\", or \"install bmad at the pin\".\n---\n\n# tk-studio-install\n\nInstalls the BMad base into a project at exactly the versions `bmad.lock` pins\n(AD-1). The upstream installer does all the work — this skill only renders the\npinned invocation, verifies the result, and measures the outcome.\n\n## Behavior (both modes)\n\n1. Run the installer script through the plugin root:\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Ftk-studio-install\u002Fscripts\u002Finstall_base.py\" --directory \u003Cproject-root>\n   ```\n\n   Optional: `--modules a,b,c` to install a subset of the lock's module set\n   (the project's configured module set once project config exists, Epic 2);\n   `--dry-run` to show the exact `npx` command without running it;\n   `--no-normalize` to keep the upstream installer's output byte-for-byte.\n\n2. The script is the whole flow: parse lock → run\n   `npx bmad-method@\u003Cpin> install` non-interactively (`--yes`, per-module\n   `--pin` flags, stdin closed) → verify `_bmad\u002F_config\u002Fmanifest.yaml` matches\n   every pin → emit one `install-outcome` event (success, or failure with the\n   failing step) → normalize the reinstall's no-op churn. Trust its JSON\n   output; do not re-run the installer by hand.\n\n   Normalization (EP-011 D2, shared with `tk-studio-base-update`) runs only\n   after verify-at-pin passes, and only when the project root is a git\n   top-level with `_bmad\u002F` tracked. An untracked or ignored `_bmad\u002F` has no\n   committed tree to be a no-op against. It restores files upstream rewrote to something provably\n   equivalent to the committed blob — line endings, list values re-serialized\n   as JSON strings, manifest `lastUpdated` stamps, derivative\n   `files-manifest.csv` hashes — and drops `*.bak` copies identical to the\n   committed file. Anything already dirty before the run is left alone. The\n   result's `normalized` object carries per-class counts and `remaining`:\n   entries that still differ from HEAD because upstream changed them for real.\n\n   Base patches (0.1.17) are re-applied before normalization: the studio's\n   declared fixes to installer-owned files (`base-patches\u002Fpatches.json`,\n   `lib\u002Fbasepatch.py`), each pinned to one upstream issue, the exact upstream\n   text it replaces, and the core versions it was verified at. A reinstall\n   therefore never silently reverts one. The result's `base_patches` lists\n   each patch's state.\n\n3. Report:\n   - **Attended:** state the installed core\u002Fmodule versions, or on failure the\n     failing step (`upstream-installer` vs `verify-at-pin`) and its detail.\n     When `normalized.remaining` is 0 the install was a no-op against the\n     committed tree — say so. When it is above 0, the installer wrote real\n     changes at this pin: in the studio repo those land through\n     `tk-studio-base-update` (a same-version re-affirmation), never a hand\n     commit; in any other project they are the project's to review and\n     commit. `normalized.skipped` names why normalization did not run.\n     Name every base patch whose state is `stale` or `unverified-core` with\n     its upstream issue: the upstream file changed or the core moved, so the\n     patch was NOT applied and must be re-verified (retire it if the issue is\n     fixed at the pin).\n   - **Headless:** no prompts (AD-11). End with the status block — `complete`\n     on exit 0; `blocked` with the failing step as `reason` otherwise:\n\n     ```json\n     {\"status\": \"complete\", \"intent\": \"tk-studio-install\", \"artifacts\": [\"_bmad\u002F\"], \"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 edit anything under `_bmad\u002F` — upstream owns that tree (NFR1); a bad\n  install is fixed by rerunning at the pin, never by patching. Normalization\n  is not an edit: it only restores committed bytes upstream itself wrote.\n- Never bump a pin here — pin changes are `tk-studio-base-update`'s job alone.\n- A long installer run is normal (npx cold cache); the script caps it with\n  `--timeout` (default 900s) rather than hanging forever.\n","# tk-studio-install\n\nInstalls the BMad base into a project at exactly the versions `bmad.lock` pins\n(AD-1). The upstream installer does all the work — this skill only renders the\npinned invocation, verifies the result, and measures the outcome.\n\n## Behavior (both modes)\n\n1. Run the installer script through the plugin root:\n\n   ```bash\n   uv run \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Ftk-studio-install\u002Fscripts\u002Finstall_base.py\" --directory \u003Cproject-root>\n   ```\n\n   Optional: `--modules a,b,c` to install a subset of the lock's module set\n   (the project's configured module set once project config exists, Epic 2);\n   `--dry-run` to show the exact `npx` command without running it;\n   `--no-normalize` to keep the upstream installer's output byte-for-byte.\n\n2. The script is the whole flow: parse lock → run\n   `npx bmad-method@\u003Cpin> install` non-interactively (`--yes`, per-module\n   `--pin` flags, stdin closed) → verify `_bmad\u002F_config\u002Fmanifest.yaml` matches\n   every pin → emit one `install-outcome` event (success, or failure with the\n   failing step) → normalize the reinstall's no-op churn. Trust its JSON\n   output; do not re-run the installer by hand.\n\n   Normalization (EP-011 D2, shared with `tk-studio-base-update`) runs only\n   after verify-at-pin passes, and only when the project root is a git\n   top-level with `_bmad\u002F` tracked. An untracked or ignored `_bmad\u002F` has no\n   committed tree to be a no-op against. It restores files upstream rewrote to something provably\n   equivalent to the committed blob — line endings, list values re-serialized\n   as JSON strings, manifest `lastUpdated` stamps, derivative\n   `files-manifest.csv` hashes — and drops `*.bak` copies identical to the\n   committed file. Anything already dirty before the run is left alone. The\n   result's `normalized` object carries per-class counts and `remaining`:\n   entries that still differ from HEAD because upstream changed them for real.\n\n   Base patches (0.1.17) are re-applied before normalization: the studio's\n   declared fixes to installer-owned files (`base-patches\u002Fpatches.json`,\n   `lib\u002Fbasepatch.py`), each pinned to one upstream issue, the exact upstream\n   text it replaces, and the core versions it was verified at. A reinstall\n   therefore never silently reverts one. The result's `base_patches` lists\n   each patch's state.\n\n3. Report:\n   - **Attended:** state the installed core\u002Fmodule versions, or on failure the\n     failing step (`upstream-installer` vs `verify-at-pin`) and its detail.\n     When `normalized.remaining` is 0 the install was a no-op against the\n     committed tree — say so. When it is above 0, the installer wrote real\n     changes at this pin: in the studio repo those land through\n     `tk-studio-base-update` (a same-version re-affirmation), never a hand\n     commit; in any other project they are the project's to review and\n     commit. `normalized.skipped` names why normalization did not run.\n     Name every base patch whose state is `stale` or `unverified-core` with\n     its upstream issue: the upstream file changed or the core moved, so the\n     patch was NOT applied and must be re-verified (retire it if the issue is\n     fixed at the pin).\n   - **Headless:** no prompts (AD-11). End with the status block — `complete`\n     on exit 0; `blocked` with the failing step as `reason` otherwise:\n\n     ```json\n     {\"status\": \"complete\", \"intent\": \"tk-studio-install\", \"artifacts\": [\"_bmad\u002F\"], \"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 edit anything under `_bmad\u002F` — upstream owns that tree (NFR1); a bad\n  install is fixed by rerunning at the pin, never by patching. Normalization\n  is not an edit: it only restores committed bytes upstream itself wrote.\n- Never bump a pin here — pin changes are `tk-studio-base-update`'s job alone.\n- A long installer run is normal (npx cold cache); the script caps it with\n  `--timeout` (default 900s) rather than hanging forever.\n",{"name":5,"description":7},"main","ecd23b3c0458cd511812f643d9111e3d7c8235f4","plugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-install","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-install",{"tool":38,"command":39},"bunx","bunx skills add thkennedy\u002Ftk-studio --skill tk-studio-install",{"tool":41,"command":42},"pnpm","pnpm dlx skills add thkennedy\u002Ftk-studio --skill tk-studio-install","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-install\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"customize.toml","OTHER","其他",470,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-install\u002Fcustomize.toml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Finstall_base.py","SCRIPT","脚本",10081,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-install\u002Fscripts\u002Finstall_base.py",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79RY33VMYR5YNPVFKWRNW9S","tk-studio-playable-judge","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\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]