[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AACK47B92A5NFJFTG087CG":3,"skill-same:01M7AACK47B92A5NFJFTG087CG":59},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AACK47B92A5NFJFTG087CG","write-plan",null,"Write a project plan file (PLAN.md) capturing a piece of work's title and owner. Use when someone asks to draft, create, start, or write up a plan for a project, feature, or migration.","JasperHG90\u002Fshakedown","JasperHG90","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8079803?v=4","01M7AAAKN62DYZ9XRCXAN0HGEF","Jasper Ginn","01M7AAAKP8D78B8ANVKEV7MRK8",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fexamples\u002Fwrite-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-plan\ndescription: Write a project plan file (PLAN.md) capturing a piece of work's title and owner. Use when someone asks to draft, create, start, or write up a plan for a project, feature, or migration.\n---\n\n# write-plan\n\nA plan needs two facts: what the work is called, and who owns it.\n\n## Ask for what you were not given\n\nTake whatever the request already supplies. For anything missing, ask the\nuser before writing, and wait for their answer.\n\nDo not invent a value and do not substitute a placeholder like \"TBD\". A\nplan with a guessed owner is worse than no plan, because it looks decided.\n\n## Write it with planctl, never yourself\n\n`PLAN.md` is written only by the CLI:\n\n```\nplanctl write --title \u003Ctitle> --owner \u003Cowner>\n```\n\nDo not create or edit `PLAN.md` with your own file-writing tools, and do\nnot write it through a shell redirect. The CLI owns the file's format.\n","# write-plan\n\nA plan needs two facts: what the work is called, and who owns it.\n\n## Ask for what you were not given\n\nTake whatever the request already supplies. For anything missing, ask the\nuser before writing, and wait for their answer.\n\nDo not invent a value and do not substitute a placeholder like \"TBD\". A\nplan with a guessed owner is worse than no plan, because it looks decided.\n\n## Write it with planctl, never yourself\n\n`PLAN.md` is written only by the CLI:\n\n```\nplanctl write --title \u003Ctitle> --owner \u003Cowner>\n```\n\nDo not create or edit `PLAN.md` with your own file-writing tools, and do\nnot write it through a shell redirect. The CLI owns the file's format.\n",{"name":5,"description":7},"main","3ac632ac167bd480d8b07868b7001fc52e2a402c","examples\u002Fwrite-plan",0,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown","https:\u002F\u002Fgithub.com\u002FJasperHG90","https:\u002F\u002Fjasperhg90.github.io\u002F","Data Engineer @ Xebia Data. I am interested in data analysis, history, politics, education, policy making and writing. ","2026-09-21 04:18:57",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JasperHG90\u002Fshakedown --skill write-plan",{"tool":39,"command":40},"bunx","bunx skills add JasperHG90\u002Fshakedown --skill write-plan",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JasperHG90\u002Fshakedown --skill write-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fexamples\u002Fwrite-plan\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"bin\u002Fplanctl","OTHER","其他",906,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fexamples\u002Fwrite-plan\u002Fbin\u002Fplanctl",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",1600,"https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fexamples\u002Fwrite-plan\u002FREADME.md",[60,67,74,81,88,95],{"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},"01M7AAFD8Q4CRZ5V34GB5655FX","fake-skill","A skill used only by shakedown's own offline tests.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Ftests\u002Ffake\u002Fskill\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},"01M7AAFB03PDQMX0DY841ADDR9","shakedown-canary","Run the shakedown canary check. Use whenever someone asks to run the canary check, verify the harness, or confirm shakedown is wired up correctly.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fsrc\u002Fshakedown\u002Fcanary\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},"01M7AAF55DP6C2XSF7N23STFP3","create-cases","Author a shakedown cases file (`shakedowns\u002F\u003Cslug>.cases.toml`) for an existing agent skill: read the skill, turn what it promises into cases, supply fixtures for the commands it must not really run, and check the result with `shakedown case validate`. Use this whenever someone wants to measure, smoke-test, or add conformance cases for a skill, asks \"how do I test this skill\", points at a SKILL.md and wants cases written, or is editing a `.cases.toml`. Use it even when they only name the skill (\"write cases for connect-agent-to-hub\") without mentioning shakedown or TOML.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-cases\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},"01M7AAEXCDG258QRVSSFQV0MV9","analyze-results","Read a shakedown report (`shakedown-report.json`) and say which file to open: the measured skill's own `SKILL.md`, the `shakedowns\u002F\u003Cslug>.cases.toml` holding its cases, the harness block in `shakedown.toml`, or a flag on the run itself. Use this whenever someone has run `shakedown case run` and wants to know what a number means or what to do about it, pastes a report or the PR comment rendered from one, asks why `skill_fired`, `tool_used`, `artifact_created` or `inputs_resolved` came out low, asks whether a rate is worth acting on, or says a conformance run failed and they cannot tell whose fault it is. Use it even when they only quote the percentage (\"my skill scores 60% on inputs_resolved, now what\") without naming shakedown or the report file.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fanalyze-results\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},"01M7AAEMM68JP8A128WHMTJJTX","add-harness","Add a new agent harness (opencode, Gemini CLI, Codex, Amp, a local Ollama-backed runner, or any CLI that loads skills) to a shakedown config so its skill conformance can be measured, and diagnose a harness that `shakedown doctor` reports as not qualifying. Use this whenever someone wants shakedown to run against a harness it does not yet support, asks why a harness fails doctor, asks how to point an existing harness at a different model or provider, or is editing the `[harness.*]` block of a shakedown.toml. Use it even when they only name the tool (\"can this test opencode?\") without mentioning config or TOML.","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fskills\u002Fadd-harness\u002FSKILL.md",[],[],{"skillNo":96,"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":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AAEEKJAS0KAJRM74K7FEFJ","https:\u002F\u002Fgithub.com\u002FJasperHG90\u002Fshakedown\u002Fblob\u002Fmain\u002Fplugins\u002Fopencode\u002Fskills\u002Fcreate-cases\u002FSKILL.md",[],[]]