[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K5507XTGE1CFJG3HGE85P":3,"skill-same:01M71K5507XTGE1CFJG3HGE85P":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":13,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M71K5507XTGE1CFJG3HGE85P","shdoc-shell-docs",null,"Write and review shellscript documentation with shdoc annotations. Use when creating, editing, or reviewing `.sh` files or shell executables that need `@file`, `@brief`, `@description`, `@arg`, `@option`, and `@example` comments added, repaired, or normalized to match shdoc conventions.","mryfmo\u002Fdotfiles","mryfmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11512262?v=4","01M71K2RDZFFQKYGMHMS5Y9PW1","01M71K2REKJ0WS61PNFQPTYP5T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fshdoc-shell-docs\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"shdoc shell docs","docs","shell","review","annotations","file","comments","when","use","match","files","conventions","write","option","editing","example","brief","with","documentation","2026-11-10 10:12:30",false,"---\nname: shdoc-shell-docs\ndescription: Write and review shellscript documentation with shdoc annotations. Use when creating, editing, or reviewing `.sh` files or shell executables that need `@file`, `@brief`, `@description`, `@arg`, `@option`, and `@example` comments added, repaired, or normalized to match shdoc conventions.\n---\n\n# Shdoc Shell Docs\n\n## Overview\n\nUse this skill to make shellscript comments parseable by `shdoc` without bloating simple code with boilerplate. Inspect the file first, then document the script and the non-trivial functions that benefit from generated reference docs.\n\n## Workflow\n\n1. Inspect the target shell file before writing comments.\n2. Read `references\u002Fshdoc-rules.md` before editing comments.\n3. Use `scripts\u002Fgenerate-docs.sh` as the repo-local style example when working in this repository.\n4. Add or repair file-level annotations near the top of the file:\n   - Prefer `@file` for the script identifier.\n   - Add `@brief` for a single-sentence summary.\n   - Add multiline `@description` only when the script needs more context.\n5. Add function-level annotations only where they help:\n   - Start with `@description`.\n   - Add `@arg` for positional parameters.\n   - Add `@option` for flags and option-value pairs.\n   - Add `@example` when the call shape is not obvious.\n   - Add `@stdout`, `@stderr`, `@exitcode`, or `@see` only when they clarify observable behavior.\n6. Rewrite existing free-form comments into valid `shdoc` annotations instead of keeping two parallel comment styles.\n\n## Review Checklist\n\n- Confirm the docs match the implementation instead of guessing arguments or options.\n- Keep annotations immediately above the file header or function they describe.\n- Prefer behavior and operator-facing intent over internal implementation notes.\n- Skip boilerplate comments for trivial private helpers unless the user asks for exhaustive coverage.\n- Keep multiline annotation blocks compact and easy to render as Markdown.\n\n## References\n\n- Read `references\u002Fshdoc-rules.md` for the minimal tag set, concise examples, and external reference policy.\n","# Shdoc Shell Docs\n\n## Overview\n\nUse this skill to make shellscript comments parseable by `shdoc` without bloating simple code with boilerplate. Inspect the file first, then document the script and the non-trivial functions that benefit from generated reference docs.\n\n## Workflow\n\n1. Inspect the target shell file before writing comments.\n2. Read `references\u002Fshdoc-rules.md` before editing comments.\n3. Use `scripts\u002Fgenerate-docs.sh` as the repo-local style example when working in this repository.\n4. Add or repair file-level annotations near the top of the file:\n   - Prefer `@file` for the script identifier.\n   - Add `@brief` for a single-sentence summary.\n   - Add multiline `@description` only when the script needs more context.\n5. Add function-level annotations only where they help:\n   - Start with `@description`.\n   - Add `@arg` for positional parameters.\n   - Add `@option` for flags and option-value pairs.\n   - Add `@example` when the call shape is not obvious.\n   - Add `@stdout`, `@stderr`, `@exitcode`, or `@see` only when they clarify observable behavior.\n6. Rewrite existing free-form comments into valid `shdoc` annotations instead of keeping two parallel comment styles.\n\n## Review Checklist\n\n- Confirm the docs match the implementation instead of guessing arguments or options.\n- Keep annotations immediately above the file header or function they describe.\n- Prefer behavior and operator-facing intent over internal implementation notes.\n- Skip boilerplate comments for trivial private helpers unless the user asks for exhaustive coverage.\n- Keep multiline annotation blocks compact and easy to render as Markdown.\n\n## References\n\n- Read `references\u002Fshdoc-rules.md` for the minimal tag set, concise examples, and external reference policy.\n",{"name":5,"description":7},"main","af601a97567f1f07e9337cad899506f601f419f1","home\u002Fdot_agents\u002Fskills\u002Fshdoc-shell-docs","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmryfmo","2026-11-14 19:17:29",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add mryfmo\u002Fdotfiles --skill shdoc-shell-docs",{"tool":54,"command":55},"bunx","bunx skills add mryfmo\u002Fdotfiles --skill shdoc-shell-docs",{"tool":57,"command":58},"pnpm","pnpm dlx skills add mryfmo\u002Fdotfiles --skill shdoc-shell-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fshdoc-shell-docs\u002FSKILL.md",true,[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"agents\u002Fopenai.yaml","REFERENCE","参考文档",212,"https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fshdoc-shell-docs\u002Fagents\u002Fopenai.yaml",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fshdoc-rules.md",2550,"https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fshdoc-shell-docs\u002Freferences\u002Fshdoc-rules.md",[73,79,85,114,136,155],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":37},"01M71K61D634ATEV8NWTGGWNGS","x","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":37},"01M71K605VRE3ABPN1MZHJNZ29","y","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fdocs\u002Fskills\u002Fy\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":37},"01M71K5Y3XX1PYZAWA7M5RG9VD","status-report","Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green\u002Fyellow\u002Fred status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fstatus-report\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[97,98,99,100,101,102,103,104,35,105,106,107,108,109,110,26,25,111,112,113],"status report","report","status","tracker","health","generate","leadership","narrative","weekly","attention","green","for","project","writing","decisions","team","project health",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":37},"01M71K5VJAHGE1NH22BGBXP693","runbook","Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frunbook\u002FSKILL.md",[],[116,121,122,123,124,125,126,127,128,25,129,130,26,110,131,132,108,133,134,135],"task","update","name","run","process","operational","create","call","ops","Existing","knowledge","rollback","escalation","recurring","things",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":37},"01M71K5SJ0FT7KD82E7PJCGATX","risk-assessment","Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[143,144,145,35,146,147,148,25,149,150,151,152,153,125,109,126,154],"risk assessment","assessment","risk","decision","user","Wrong","go","assess","trigger","risk register","vendor","register",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":37},"01M71K5PYD2A2BDM6KMZ8F01SV","change-request","Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[162,163,164,26,35,165,166,21,167,168,169,25,170,171,172,173,174,108,175,145],"request","change request","change","communications","stakeholder communications","rollback plan","analysis","rollout","impact","change management","impact analysis","system","deployment","planning"]