[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6HRAZ6R5QBZAXPP7Q5EC0":3,"skill-same:01M7E6HRAZ6R5QBZAXPP7Q5EC0":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7E6HRAZ6R5QBZAXPP7Q5EC0","game",null,"Use when the user asks where the game stands, what to work on next, or to bring the plan and its GitHub Project up to date.","nick-vas\u002Fhyperdot","nick-vas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7181961?v=4","01M7E6F6F0BQ49V0JZHX9BXCBD","Nikolaos Vasilikiotis","01M7E6F6FZW8SW1AJ1S7ARFE89",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgame\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game\ndescription: Use when the user asks where the game stands, what to work on next, or to bring the plan and its GitHub Project up to date.\ndisable-model-invocation: true\n---\n\n# \u002Fgame: where the game is, and what next\n\n`status` gathers the facts; you judge them, and every judgement cites its evidence. What you conclude goes into files\nthe user can read (`docs\u002FGDD.md`, `plan\u002FSTATUS.md`, `plan\u002Fplan.json`); the GitHub Project mirrors the plan, and when the\nuser has moved an item, the user's move wins.\n\n## 1. Facts\n\n```powershell\npwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 status -Json      # add -Project \u003Cdir> when the game is not the current folder\n```\n\n`features[]` (with `taggedTests`, `tasks`, `testedAndPassing`), `plan` (phase, open gates, tasks with `itemId` and\n`boardColumn`), `runs` (latest run per command), `git`, `inventory`, `suggestedCommands` (kit commands that are due, each with its reason), `handoffs` (what the `godot-verifier` and\n`godot-architect` subagents were last asked and answered, newest first), `warnings`. If `runs.test` is missing or older than\n`git.lastCommit`, run `test -Json -Quiet` first so the evidence is current.\n\n## 2. The GDD (first run only)\n\nIf `gdd` is null, draft `docs\u002FGDD.md` from `${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002FGDD.md`. Base it on what exists:\n`inventory` (scenes, main scene, autoloads, input actions), the scripts behind them, and any notes in the repository.\nEach feature gets an id (F1, F2...), a guessed priority, the kinds of fun it serves (`Fun:`, from `game-design`) and\n\"Done when\" lines describing behaviour you can see in the code. Keep `Status: draft` in it. A game jam entry starts from\n`${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002FGDD-jam.md` instead (`game-plan`, jam mode).\n\nThen confirm it with the user, section by section, with multiple-choice questions: pitch and pillars, audience, core\nloop, the first session, then features in groups of at most four (Keep, Change, Drop, Later), then out of scope; the\nother sections only when the user wants them. Write each answer in before the next question. Remove `Status: draft` only when every section is confirmed. Never measure progress against a draft.\n\nAsk once whether to tag existing tests: a `GDD:F\u003Cn>` comment on each test that checks a feature's \"Done when\", so\n`status` can find the proof next time.\n\n### First-session stubs\n\n`gdd.firstSession` lists the GDD's first-session steps (`S1`, `S2`...), each with the `tests` and `stubs` tagged\n`GDD:S\u003Cn>`. Once the GDD is confirmed, write a stub for each step that has neither:\n\n- `test\u002Fflows\u002Ffirst_session_s\u003Cn>.stub.json`: a flow in the `ui-flows` format, `\"name\": \"GDD:S\u003Cn> \u003Cthe step>\"`,\n  `scene` the main scene, and as `steps` what the step says the player does and sees, as far as the node paths exist.\n- One `playthrough.stub.json` beside `project.godot`: `\"covers\"` lists every step's `GDD:S\u003Cn>`, `\"expect\"` one log line\n  a step's milestone prints (`\"[Run] S3 exit reached\"`), the ending last (the `playthrough` runner's format).\n\nNo runner plays a `.stub.json`, so stubs never turn a run red. Each stubbed step gets a task\n(`plan -Do add -Title \"S2 \u003Cstep> - flow\" -Column backlog`). Starting it renames the stub to `.flow.json`, finishes it and\nwatches it fail before the code (`godot-test-loop`); `playthrough.stub.json` becomes `playthrough.json` once the game's\n`--autoplay` bot exists (`automation-hooks`).\n\n## 3. Assess every feature\n\n| Mark | Meaning | Evidence to cite |\n|---|---|---|\n| missing | no code for it | where you looked |\n| started | code exists, some \"Done when\" lines are not met | files, the unmet lines |\n| works | the code meets every \"Done when\" line, but no tagged test proves it | files, a passing smoke or flow run |\n| proven | tagged tests or flows cover every \"Done when\" line, and the latest test run passed | test names (`file:line`), run time |\n\n### Design and architecture review\n\nTests passing is not the whole picture. Look for at most five problems, design first, each one line with its evidence;\nleave out anything without evidence, and fix nothing here (each finding becomes a task in step 4 or a question in step 6):\n\n- **Design:** a must or should feature with no `Fun:` line, or serving none of the game's main kinds of fun; tasks in\n  `doing` for `could` features while `must` features are missing; code for something the GDD does not have; a core loop\n  (the GDD's) that no tagged test or flow plays through.\n- **Architecture:** the `architecture` runner's `warnings` in the latest `test -Json` you ran (run\n  `test -Json -Quiet -Runners architecture` if there is none this session), most frequent rule first; an autoload in\n  `inventory.autoloads` that no file in `docs\u002Fdecisions\u002F` names; `docs\u002FARCHITECTURE.md` missing once the game has an\n  autoload or a decision, or its autoloads and main scene differ from `inventory` (the `godot-architect` subagent writes\n  and updates it); decisions still `Proposed`; a `todoCount` that keeps\n  growing; `handoffs` where the verifier's latest verdict for a check is a FAIL with nothing passing after it, or an\n  architect proposal nobody answered.\n\nWrite `plan\u002FSTATUS.md` (replace it each run): the date and current phase with its open gates; a table Feature | Priority |\nMark | Evidence | Next step; a \"Review\" section with the findings above (or \"nothing found\", with what you looked at);\nthe `warnings` worth acting on; the `decisions` still `Proposed`, which wait for the user; and a \"Board changes\" section\n(step 5).\n\n## 4. Plan tasks\n\nEvery feature that is not proven and not `won't` needs a task:\n`plan -Do add -Title \"\u003Cfeature> - \u003Cnext step>\" -Feature F3 -Column backlog`. A proven feature's tasks go to `done`\n(`plan -Do move -Id t3 -Column done`; several at once as `-Id t3,t4,t5`, one call instead of three). `plan -Do move` refuses\n`doing` past the work-in-progress limit; finish or move something back instead. A task for a feature the user dropped goes with `plan -Do remove -Id t3`.\n\n## 5. The GitHub Project\n\nThe project is `projectBoard` in `plan -Json` (`\u003Cowner>\u002F\u003Cnumber>`), shown as `plan.board` in `status`. `plan -Do sync` does\nthis whole step with the GitHub CLI (signed in with the project scope: `gh auth refresh -s project`), so no connector is\nneeded. If there is no project yet, make one: `plan -Do sync -Board @me` (or the owner's login) creates a private project\ntitled \"\u003Cgame> plan\" with a Column field (Backlog, Design, To Do, Doing, Testing, Done), links it to the game's repository\nand puts every task on it; tell the user to set the project's Board view to group by Column (`gh project view \u003Cnumber>\n--owner \u003Cowner> --web`), which the CLI cannot do. To use a project that exists, `plan -Do link -Board \u003Cowner>\u002F\u003Cnumber>`.\n`-Column` takes either the column or the option's name, and `-Item` takes a project item id (`PVTI_...`).\n\nRun `plan -Do sync` and read `sync` in the result:\n- `moved` tasks were moved by the user on the board: the board wins, and the plan has been updated.\n- `itemsMoved` items followed a task you moved in the plan; `created` items are new tasks; `archived` items belonged to\n  removed tasks.\n- `imported` tasks are items the user added on the board; if one is not in the GDD, raise it under the scope rule below.\n- `warnings` name items that are gone or that the kit made for a task nobody links; mention them.\n\nList every item created or moved under \"Board changes\" in `STATUS.md`. If `sync` fails with `project-credentials`, tell\nthe user to run `gh auth refresh -s project` and carry on with the plan alone. The plugin's Stop hook runs the same sync\nafter a turn that changed the plan (`HYPERDOT_PROJECT_SYNC=off` stops it), so the board is rarely behind.\n\n## 6. What next\n\nRun the `suggestedCommands` whose reason is a failed or missing run before judging (a stale `test` makes every mark below unreliable), and list the rest under \"Checks due\" in `STATUS.md`. End with one multiple-choice question: the three best next tasks, each with its reason in one line (must-haves first,\nthen what unblocks the current phase's gates, then risks from `warnings` and the review), and \"Something else\". When the user picks\none, move it to `doing` in the plan (the sync moves the item), and start it with `godot-test-loop`.\n\n## Scope rules\n\n- **Not in the GDD:** before building anything the GDD does not contain, ask: add it as a new feature (with priority\n  and \"Done when\"), or drop it. Never build it silently.\n- **New structure:** a next task that adds a system, an autoload or a dependency between scenes starts with the\n  `godot-architect` subagent, and its decision is accepted before code is written.\n- **Too much in progress:** respect the work-in-progress limit; suggest finishing a task instead of starting one.\n- **Over the timebox:** when the phase is past its timebox, propose which `could` and `should` features to cut, starting\n  with those that serve none of the game's main kinds of fun. Never propose cutting tests.\n- **Pixel art:** a next task that draws or animates sprites starts by checking `.mcp.json` for an `aseprite` server. If it is\n  missing and the user draws in Aseprite, offer `init -McpAseprite \"\u003Cthe folder or Aseprite.exe>\"` (`godot-editor-bridge`);\n  ask for the path, never guess it.\n- **Is it fun:** a new feature names the kind of fun it serves before it is built; if it serves none of the game's main\n  kinds, say so when you ask whether to add it (`game-design`).\n\n## Kit notes\n\nWhen the kit gets in the way during the session (a command or flag that is wrong or missing, a confusing error, a check\nthat misses or misfires, a skill that sent you the wrong way, a step that took several tries), append one line to\n`docs\u002Fkit-notes.md` in the game, in the format at its top: `yyyy-mm-dd \u003Ccommand, skill or subagent>: \u003Cwhat got in the\nway> - \u003Cwhat would have helped>`. Create the file from `${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002Fkit-notes.md` if it is\nmissing. Do not change the kit from the game's chat; `\u002Fretro` and the weekly review turn the notes into proposals.\n","# \u002Fgame: where the game is, and what next\n\n`status` gathers the facts; you judge them, and every judgement cites its evidence. What you conclude goes into files\nthe user can read (`docs\u002FGDD.md`, `plan\u002FSTATUS.md`, `plan\u002Fplan.json`); the GitHub Project mirrors the plan, and when the\nuser has moved an item, the user's move wins.\n\n## 1. Facts\n\n```powershell\npwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 status -Json      # add -Project \u003Cdir> when the game is not the current folder\n```\n\n`features[]` (with `taggedTests`, `tasks`, `testedAndPassing`), `plan` (phase, open gates, tasks with `itemId` and\n`boardColumn`), `runs` (latest run per command), `git`, `inventory`, `suggestedCommands` (kit commands that are due, each with its reason), `handoffs` (what the `godot-verifier` and\n`godot-architect` subagents were last asked and answered, newest first), `warnings`. If `runs.test` is missing or older than\n`git.lastCommit`, run `test -Json -Quiet` first so the evidence is current.\n\n## 2. The GDD (first run only)\n\nIf `gdd` is null, draft `docs\u002FGDD.md` from `${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002FGDD.md`. Base it on what exists:\n`inventory` (scenes, main scene, autoloads, input actions), the scripts behind them, and any notes in the repository.\nEach feature gets an id (F1, F2...), a guessed priority, the kinds of fun it serves (`Fun:`, from `game-design`) and\n\"Done when\" lines describing behaviour you can see in the code. Keep `Status: draft` in it. A game jam entry starts from\n`${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002FGDD-jam.md` instead (`game-plan`, jam mode).\n\nThen confirm it with the user, section by section, with multiple-choice questions: pitch and pillars, audience, core\nloop, the first session, then features in groups of at most four (Keep, Change, Drop, Later), then out of scope; the\nother sections only when the user wants them. Write each answer in before the next question. Remove `Status: draft` only when every section is confirmed. Never measure progress against a draft.\n\nAsk once whether to tag existing tests: a `GDD:F\u003Cn>` comment on each test that checks a feature's \"Done when\", so\n`status` can find the proof next time.\n\n### First-session stubs\n\n`gdd.firstSession` lists the GDD's first-session steps (`S1`, `S2`...), each with the `tests` and `stubs` tagged\n`GDD:S\u003Cn>`. Once the GDD is confirmed, write a stub for each step that has neither:\n\n- `test\u002Fflows\u002Ffirst_session_s\u003Cn>.stub.json`: a flow in the `ui-flows` format, `\"name\": \"GDD:S\u003Cn> \u003Cthe step>\"`,\n  `scene` the main scene, and as `steps` what the step says the player does and sees, as far as the node paths exist.\n- One `playthrough.stub.json` beside `project.godot`: `\"covers\"` lists every step's `GDD:S\u003Cn>`, `\"expect\"` one log line\n  a step's milestone prints (`\"[Run] S3 exit reached\"`), the ending last (the `playthrough` runner's format).\n\nNo runner plays a `.stub.json`, so stubs never turn a run red. Each stubbed step gets a task\n(`plan -Do add -Title \"S2 \u003Cstep> - flow\" -Column backlog`). Starting it renames the stub to `.flow.json`, finishes it and\nwatches it fail before the code (`godot-test-loop`); `playthrough.stub.json` becomes `playthrough.json` once the game's\n`--autoplay` bot exists (`automation-hooks`).\n\n## 3. Assess every feature\n\n| Mark | Meaning | Evidence to cite |\n|---|---|---|\n| missing | no code for it | where you looked |\n| started | code exists, some \"Done when\" lines are not met | files, the unmet lines |\n| works | the code meets every \"Done when\" line, but no tagged test proves it | files, a passing smoke or flow run |\n| proven | tagged tests or flows cover every \"Done when\" line, and the latest test run passed | test names (`file:line`), run time |\n\n### Design and architecture review\n\nTests passing is not the whole picture. Look for at most five problems, design first, each one line with its evidence;\nleave out anything without evidence, and fix nothing here (each finding becomes a task in step 4 or a question in step 6):\n\n- **Design:** a must or should feature with no `Fun:` line, or serving none of the game's main kinds of fun; tasks in\n  `doing` for `could` features while `must` features are missing; code for something the GDD does not have; a core loop\n  (the GDD's) that no tagged test or flow plays through.\n- **Architecture:** the `architecture` runner's `warnings` in the latest `test -Json` you ran (run\n  `test -Json -Quiet -Runners architecture` if there is none this session), most frequent rule first; an autoload in\n  `inventory.autoloads` that no file in `docs\u002Fdecisions\u002F` names; `docs\u002FARCHITECTURE.md` missing once the game has an\n  autoload or a decision, or its autoloads and main scene differ from `inventory` (the `godot-architect` subagent writes\n  and updates it); decisions still `Proposed`; a `todoCount` that keeps\n  growing; `handoffs` where the verifier's latest verdict for a check is a FAIL with nothing passing after it, or an\n  architect proposal nobody answered.\n\nWrite `plan\u002FSTATUS.md` (replace it each run): the date and current phase with its open gates; a table Feature | Priority |\nMark | Evidence | Next step; a \"Review\" section with the findings above (or \"nothing found\", with what you looked at);\nthe `warnings` worth acting on; the `decisions` still `Proposed`, which wait for the user; and a \"Board changes\" section\n(step 5).\n\n## 4. Plan tasks\n\nEvery feature that is not proven and not `won't` needs a task:\n`plan -Do add -Title \"\u003Cfeature> - \u003Cnext step>\" -Feature F3 -Column backlog`. A proven feature's tasks go to `done`\n(`plan -Do move -Id t3 -Column done`; several at once as `-Id t3,t4,t5`, one call instead of three). `plan -Do move` refuses\n`doing` past the work-in-progress limit; finish or move something back instead. A task for a feature the user dropped goes with `plan -Do remove -Id t3`.\n\n## 5. The GitHub Project\n\nThe project is `projectBoard` in `plan -Json` (`\u003Cowner>\u002F\u003Cnumber>`), shown as `plan.board` in `status`. `plan -Do sync` does\nthis whole step with the GitHub CLI (signed in with the project scope: `gh auth refresh -s project`), so no connector is\nneeded. If there is no project yet, make one: `plan -Do sync -Board @me` (or the owner's login) creates a private project\ntitled \"\u003Cgame> plan\" with a Column field (Backlog, Design, To Do, Doing, Testing, Done), links it to the game's repository\nand puts every task on it; tell the user to set the project's Board view to group by Column (`gh project view \u003Cnumber>\n--owner \u003Cowner> --web`), which the CLI cannot do. To use a project that exists, `plan -Do link -Board \u003Cowner>\u002F\u003Cnumber>`.\n`-Column` takes either the column or the option's name, and `-Item` takes a project item id (`PVTI_...`).\n\nRun `plan -Do sync` and read `sync` in the result:\n- `moved` tasks were moved by the user on the board: the board wins, and the plan has been updated.\n- `itemsMoved` items followed a task you moved in the plan; `created` items are new tasks; `archived` items belonged to\n  removed tasks.\n- `imported` tasks are items the user added on the board; if one is not in the GDD, raise it under the scope rule below.\n- `warnings` name items that are gone or that the kit made for a task nobody links; mention them.\n\nList every item created or moved under \"Board changes\" in `STATUS.md`. If `sync` fails with `project-credentials`, tell\nthe user to run `gh auth refresh -s project` and carry on with the plan alone. The plugin's Stop hook runs the same sync\nafter a turn that changed the plan (`HYPERDOT_PROJECT_SYNC=off` stops it), so the board is rarely behind.\n\n## 6. What next\n\nRun the `suggestedCommands` whose reason is a failed or missing run before judging (a stale `test` makes every mark below unreliable), and list the rest under \"Checks due\" in `STATUS.md`. End with one multiple-choice question: the three best next tasks, each with its reason in one line (must-haves first,\nthen what unblocks the current phase's gates, then risks from `warnings` and the review), and \"Something else\". When the user picks\none, move it to `doing` in the plan (the sync moves the item), and start it with `godot-test-loop`.\n\n## Scope rules\n\n- **Not in the GDD:** before building anything the GDD does not contain, ask: add it as a new feature (with priority\n  and \"Done when\"), or drop it. Never build it silently.\n- **New structure:** a next task that adds a system, an autoload or a dependency between scenes starts with the\n  `godot-architect` subagent, and its decision is accepted before code is written.\n- **Too much in progress:** respect the work-in-progress limit; suggest finishing a task instead of starting one.\n- **Over the timebox:** when the phase is past its timebox, propose which `could` and `should` features to cut, starting\n  with those that serve none of the game's main kinds of fun. Never propose cutting tests.\n- **Pixel art:** a next task that draws or animates sprites starts by checking `.mcp.json` for an `aseprite` server. If it is\n  missing and the user draws in Aseprite, offer `init -McpAseprite \"\u003Cthe folder or Aseprite.exe>\"` (`godot-editor-bridge`);\n  ask for the path, never guess it.\n- **Is it fun:** a new feature names the kind of fun it serves before it is built; if it serves none of the game's main\n  kinds, say so when you ask whether to add it (`game-design`).\n\n## Kit notes\n\nWhen the kit gets in the way during the session (a command or flag that is wrong or missing, a confusing error, a check\nthat misses or misfires, a skill that sent you the wrong way, a step that took several tries), append one line to\n`docs\u002Fkit-notes.md` in the game, in the format at its top: `yyyy-mm-dd \u003Ccommand, skill or subagent>: \u003Cwhat got in the\nway> - \u003Cwhat would have helped>`. Create the file from `${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002Fkit-notes.md` if it is\nmissing. Do not change the kit from the game's chat; `\u002Fretro` and the weekly review turn the notes into proposals.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","5fa4c2262d814d50f72198a95b8c483ff195f90f",".agents\u002Fskills\u002Fgame",0,"https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot","https:\u002F\u002Fnick-vas.github.io\u002Fhyperdot\u002F","https:\u002F\u002Fgithub.com\u002Fnick-vas","https:\u002F\u002Fcommon-beef.itch.io\u002F","2026-11-13 18:55:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add nick-vas\u002Fhyperdot --skill game",{"tool":40,"command":41},"bunx","bunx skills add nick-vas\u002Fhyperdot --skill game",{"tool":43,"command":44},"pnpm","pnpm dlx skills add nick-vas\u002Fhyperdot --skill game","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgame\u002FSKILL.md",[],[48,55,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7E6RF2S03S92PB9RZB4S4W0","over-budget","Use when a fixture exceeds the size budget.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fover-budget\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"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":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E6RBY8SDNMA3ZARE8MAH0G","bad-yaml","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-yaml\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7E6R9S9YHTC552SR41RQAJ1","bad-workflow-description","Use when testing; runs the kit and then reads the JSON.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-workflow-description\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7E6R6CWSAN48C80130CM1AK","bad-version","Use when a fixture quotes a stale package version.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-version\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E6R2C0E24TC133ESHKZT9R","bad-value","Use when a fixture passes a value outside a parameter's set.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-value\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7E6QYM81V061X7DSQ94CZRP","bad-trigger","Helps with Godot tests.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-trigger\u002FSKILL.md",[],[]]