[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M799E64BDA48XGJMV4K5M445":3,"skill-same:01M799E64BDA48XGJMV4K5M445":45},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M799E64BDA48XGJMV4K5M445","code-tour",null,"Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured \"explain how this works\" requests.","pjherron\u002Fhypoc","pjherron","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F800763?v=4","01M799C7XC0XKKW2D6RMYNHCY8","Patrick Herron","01M799C7XZPGZ9QZ7XAQN5MQAN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fcode-tour\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-tour\ndescription: Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured \"explain how this works\" requests.\norigin: ECC\n---\n\n# Code Tour\n\nCreate **CodeTour** `.tour` files for codebase walkthroughs that open directly to real files and line ranges. Tours live in `.tours\u002F` and are meant for the CodeTour format, not ad hoc Markdown notes.\n\nA good tour is a narrative for a specific reader:\n- what they are looking at\n- why it matters\n- what path they should follow next\n\nOnly create `.tour` JSON files. Do not modify source code as part of this skill.\n\n## When to Use\n\nUse this skill when:\n- the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour\n- the user says \"explain how X works\" and wants a reusable guided artifact\n- the user wants a ramp-up path for a new engineer or reviewer\n- the task is better served by a guided sequence than a flat summary\n\nExamples:\n- onboarding a new maintainer\n- architecture tour for one service or package\n- PR-review walk-through anchored to changed files\n- RCA tour showing the failure path\n- security review tour of trust boundaries and key checks\n\n## When NOT to Use\n\n| Instead of code-tour | Use |\n| --- | --- |\n| A one-off explanation in chat is enough | answer directly |\n| The user wants prose docs, not a `.tour` artifact | `documentation-lookup` or repo docs editing |\n| The task is implementation or refactoring | do the implementation work |\n| The task is broad codebase onboarding without a tour artifact | `codebase-onboarding` |\n\n## Workflow\n\n### 1. Discover\n\nExplore the repo before writing anything:\n- README and package\u002Fapp entry points\n- folder structure\n- relevant config files\n- the changed files if the tour is PR-focused\n\nDo not start writing steps before you understand the shape of the code.\n\n### 2. Infer the reader\n\nDecide the persona and depth from the request.\n\n| Request shape | Persona | Suggested depth |\n| --- | --- | --- |\n| \"onboarding\", \"new joiner\" | `new-joiner` | 9-13 steps |\n| \"quick tour\", \"vibe check\" | `vibecoder` | 5-8 steps |\n| \"architecture\" | `architect` | 14-18 steps |\n| \"tour this PR\" | `pr-reviewer` | 7-11 steps |\n| \"why did this break\" | `rca-investigator` | 7-11 steps |\n| \"security review\" | `security-reviewer` | 7-11 steps |\n| \"explain how this feature works\" | `feature-explainer` | 7-11 steps |\n| \"debug this path\" | `bug-fixer` | 7-11 steps |\n\n### 3. Read and verify anchors\n\nEvery file path and line anchor must be real:\n- confirm the file exists\n- confirm the line numbers are in range\n- if using a selection, verify the exact block\n- if the file is volatile, prefer a pattern-based anchor\n\nNever guess line numbers.\n\n### 4. Write the `.tour`\n\nWrite to:\n\n```text\n.tours\u002F\u003Cpersona>-\u003Cfocus>.tour\n```\n\nKeep the path deterministic and readable.\n\n### 5. Validate\n\nBefore finishing:\n- every referenced path exists\n- every line or selection is valid\n- the first step is anchored to a real file or directory\n- the tour tells a coherent story rather than listing files\n\n## Step Types\n\n### Content\n\nUse sparingly, usually only for a closing step:\n\n```json\n{ \"title\": \"Next Steps\", \"description\": \"You can now trace the request path end to end.\" }\n```\n\nDo not make the first step content-only.\n\n### Directory\n\nUse to orient the reader to a module:\n\n```json\n{ \"directory\": \"src\u002Fservices\", \"title\": \"Service Layer\", \"description\": \"The core orchestration logic lives here.\" }\n```\n\n### File + line\n\nThis is the default step type:\n\n```json\n{ \"file\": \"src\u002Fauth\u002Fmiddleware.ts\", \"line\": 42, \"title\": \"Auth Gate\", \"description\": \"Every protected request passes here first.\" }\n```\n\n### Selection\n\nUse when one code block matters more than the whole file:\n\n```json\n{\n  \"file\": \"src\u002Fcore\u002Fpipeline.ts\",\n  \"selection\": {\n    \"start\": { \"line\": 15, \"character\": 0 },\n    \"end\": { \"line\": 34, \"character\": 0 }\n  },\n  \"title\": \"Request Pipeline\",\n  \"description\": \"This block wires validation, auth, and downstream execution.\"\n}\n```\n\n### Pattern\n\nUse when exact lines may drift:\n\n```json\n{ \"file\": \"src\u002Fapp.ts\", \"pattern\": \"export default class App\", \"title\": \"Application Entry\" }\n```\n\n### URI\n\nUse for PRs, issues, or docs when helpful:\n\n```json\n{ \"uri\": \"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002F456\", \"title\": \"The PR\" }\n```\n\n## Writing Rule: SMIG\n\nEach description should answer:\n- **Situation**: what the reader is looking at\n- **Mechanism**: how it works\n- **Implication**: why it matters for this persona\n- **Gotcha**: what a smart reader might miss\n\nKeep descriptions compact, specific, and grounded in the actual code.\n\n## Narrative Shape\n\nUse this arc unless the task clearly needs something different:\n1. orientation\n2. module map\n3. core execution path\n4. edge case or gotcha\n5. closing \u002F next move\n\nThe tour should feel like a path, not an inventory.\n\n## Example\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"API Service Tour\",\n  \"description\": \"Walkthrough of the request path for the payments service.\",\n  \"ref\": \"main\",\n  \"steps\": [\n    {\n      \"directory\": \"src\",\n      \"title\": \"Source Root\",\n      \"description\": \"All runtime code for the service starts here.\"\n    },\n    {\n      \"file\": \"src\u002Fserver.ts\",\n      \"line\": 12,\n      \"title\": \"Entry Point\",\n      \"description\": \"The server boots here and wires middleware before any route is reached.\"\n    },\n    {\n      \"file\": \"src\u002Froutes\u002Fpayments.ts\",\n      \"line\": 8,\n      \"title\": \"Payment Routes\",\n      \"description\": \"Every payments request enters through this router before hitting service logic.\"\n    },\n    {\n      \"title\": \"Next Steps\",\n      \"description\": \"You can now follow any payment request end to end with the main anchors in place.\"\n    }\n  ]\n}\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| Flat file listing | Tell a story with dependency between steps |\n| Generic descriptions | Name the concrete code path or pattern |\n| Guessed anchors | Verify every file and line first |\n| Too many steps for a quick tour | Cut aggressively |\n| First step is content-only | Anchor the first step to a real file or directory |\n| Persona mismatch | Write for the actual reader, not a generic engineer |\n\n## Best Practices\n\n- keep step count proportional to repo size and persona depth\n- use directory steps for orientation, file steps for substance\n- for PR tours, cover changed files first\n- for monorepos, scope to the relevant packages instead of touring everything\n- close with what the reader can now do, not a recap\n\n## Related Skills\n\n- `codebase-onboarding`\n- `coding-standards`\n- `council`\n- official upstream format: `microsoft\u002Fcodetour`\n","# Code Tour\n\nCreate **CodeTour** `.tour` files for codebase walkthroughs that open directly to real files and line ranges. Tours live in `.tours\u002F` and are meant for the CodeTour format, not ad hoc Markdown notes.\n\nA good tour is a narrative for a specific reader:\n- what they are looking at\n- why it matters\n- what path they should follow next\n\nOnly create `.tour` JSON files. Do not modify source code as part of this skill.\n\n## When to Use\n\nUse this skill when:\n- the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour\n- the user says \"explain how X works\" and wants a reusable guided artifact\n- the user wants a ramp-up path for a new engineer or reviewer\n- the task is better served by a guided sequence than a flat summary\n\nExamples:\n- onboarding a new maintainer\n- architecture tour for one service or package\n- PR-review walk-through anchored to changed files\n- RCA tour showing the failure path\n- security review tour of trust boundaries and key checks\n\n## When NOT to Use\n\n| Instead of code-tour | Use |\n| --- | --- |\n| A one-off explanation in chat is enough | answer directly |\n| The user wants prose docs, not a `.tour` artifact | `documentation-lookup` or repo docs editing |\n| The task is implementation or refactoring | do the implementation work |\n| The task is broad codebase onboarding without a tour artifact | `codebase-onboarding` |\n\n## Workflow\n\n### 1. Discover\n\nExplore the repo before writing anything:\n- README and package\u002Fapp entry points\n- folder structure\n- relevant config files\n- the changed files if the tour is PR-focused\n\nDo not start writing steps before you understand the shape of the code.\n\n### 2. Infer the reader\n\nDecide the persona and depth from the request.\n\n| Request shape | Persona | Suggested depth |\n| --- | --- | --- |\n| \"onboarding\", \"new joiner\" | `new-joiner` | 9-13 steps |\n| \"quick tour\", \"vibe check\" | `vibecoder` | 5-8 steps |\n| \"architecture\" | `architect` | 14-18 steps |\n| \"tour this PR\" | `pr-reviewer` | 7-11 steps |\n| \"why did this break\" | `rca-investigator` | 7-11 steps |\n| \"security review\" | `security-reviewer` | 7-11 steps |\n| \"explain how this feature works\" | `feature-explainer` | 7-11 steps |\n| \"debug this path\" | `bug-fixer` | 7-11 steps |\n\n### 3. Read and verify anchors\n\nEvery file path and line anchor must be real:\n- confirm the file exists\n- confirm the line numbers are in range\n- if using a selection, verify the exact block\n- if the file is volatile, prefer a pattern-based anchor\n\nNever guess line numbers.\n\n### 4. Write the `.tour`\n\nWrite to:\n\n```text\n.tours\u002F\u003Cpersona>-\u003Cfocus>.tour\n```\n\nKeep the path deterministic and readable.\n\n### 5. Validate\n\nBefore finishing:\n- every referenced path exists\n- every line or selection is valid\n- the first step is anchored to a real file or directory\n- the tour tells a coherent story rather than listing files\n\n## Step Types\n\n### Content\n\nUse sparingly, usually only for a closing step:\n\n```json\n{ \"title\": \"Next Steps\", \"description\": \"You can now trace the request path end to end.\" }\n```\n\nDo not make the first step content-only.\n\n### Directory\n\nUse to orient the reader to a module:\n\n```json\n{ \"directory\": \"src\u002Fservices\", \"title\": \"Service Layer\", \"description\": \"The core orchestration logic lives here.\" }\n```\n\n### File + line\n\nThis is the default step type:\n\n```json\n{ \"file\": \"src\u002Fauth\u002Fmiddleware.ts\", \"line\": 42, \"title\": \"Auth Gate\", \"description\": \"Every protected request passes here first.\" }\n```\n\n### Selection\n\nUse when one code block matters more than the whole file:\n\n```json\n{\n  \"file\": \"src\u002Fcore\u002Fpipeline.ts\",\n  \"selection\": {\n    \"start\": { \"line\": 15, \"character\": 0 },\n    \"end\": { \"line\": 34, \"character\": 0 }\n  },\n  \"title\": \"Request Pipeline\",\n  \"description\": \"This block wires validation, auth, and downstream execution.\"\n}\n```\n\n### Pattern\n\nUse when exact lines may drift:\n\n```json\n{ \"file\": \"src\u002Fapp.ts\", \"pattern\": \"export default class App\", \"title\": \"Application Entry\" }\n```\n\n### URI\n\nUse for PRs, issues, or docs when helpful:\n\n```json\n{ \"uri\": \"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002F456\", \"title\": \"The PR\" }\n```\n\n## Writing Rule: SMIG\n\nEach description should answer:\n- **Situation**: what the reader is looking at\n- **Mechanism**: how it works\n- **Implication**: why it matters for this persona\n- **Gotcha**: what a smart reader might miss\n\nKeep descriptions compact, specific, and grounded in the actual code.\n\n## Narrative Shape\n\nUse this arc unless the task clearly needs something different:\n1. orientation\n2. module map\n3. core execution path\n4. edge case or gotcha\n5. closing \u002F next move\n\nThe tour should feel like a path, not an inventory.\n\n## Example\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"API Service Tour\",\n  \"description\": \"Walkthrough of the request path for the payments service.\",\n  \"ref\": \"main\",\n  \"steps\": [\n    {\n      \"directory\": \"src\",\n      \"title\": \"Source Root\",\n      \"description\": \"All runtime code for the service starts here.\"\n    },\n    {\n      \"file\": \"src\u002Fserver.ts\",\n      \"line\": 12,\n      \"title\": \"Entry Point\",\n      \"description\": \"The server boots here and wires middleware before any route is reached.\"\n    },\n    {\n      \"file\": \"src\u002Froutes\u002Fpayments.ts\",\n      \"line\": 8,\n      \"title\": \"Payment Routes\",\n      \"description\": \"Every payments request enters through this router before hitting service logic.\"\n    },\n    {\n      \"title\": \"Next Steps\",\n      \"description\": \"You can now follow any payment request end to end with the main anchors in place.\"\n    }\n  ]\n}\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| Flat file listing | Tell a story with dependency between steps |\n| Generic descriptions | Name the concrete code path or pattern |\n| Guessed anchors | Verify every file and line first |\n| Too many steps for a quick tour | Cut aggressively |\n| First step is content-only | Anchor the first step to a real file or directory |\n| Persona mismatch | Write for the actual reader, not a generic engineer |\n\n## Best Practices\n\n- keep step count proportional to repo size and persona depth\n- use directory steps for orientation, file steps for substance\n- for PR tours, cover changed files first\n- for monorepos, scope to the relevant packages instead of touring everything\n- close with what the reader can now do, not a recap\n\n## Related Skills\n\n- `codebase-onboarding`\n- `coding-standards`\n- `council`\n- official upstream format: `microsoft\u002Fcodetour`\n",{"name":5,"origin":24,"description":7},"ECC","main","eebcd780d62a0710aa03028091dc1e9baa995b83","hypoc\u002Fskills\u002Fcode-tour","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc","https:\u002F\u002Fgithub.com\u002Fpjherron","2026-09-01 06:45:11",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add pjherron\u002Fhypoc --skill code-tour",{"tool":37,"command":38},"bunx","bunx skills add pjherron\u002Fhypoc --skill code-tour",{"tool":40,"command":41},"pnpm","pnpm dlx skills add pjherron\u002Fhypoc --skill code-tour","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fcode-tour\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M799MNB4RVHZZECC75ZFGH0Y","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"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},"01M799MHR27W0YV1VMW26N691S","Verification & Quality Assurance","Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fverification-quality\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},"01M799MEX0F1D253S3KZ1635PE","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fverification-loop\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},"01M799MCFN5N6A9VWM6R2TFJRK","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Ftriage\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},"01M799M695F2XJBTP21YHN0R46","token-budget-advisor","Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: \"token budget\", \"token count\", \"token usage\", \"token limit\", \"response length\", \"answer depth\", \"short version\", \"brief answer\", \"detailed answer\", \"exhaustive answer\", \"respuesta corta vs larga\", \"cuántos tokens\", \"ahorrar tokens\", \"responde al 50%\", \"dame la versión corta\", \"quiero controlar cuánto usas\", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or \"token\" refers to auth\u002Fsession\u002Fpayment tokens rather than response size.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Ftoken-budget-advisor\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},"01M799M387CZZVGC18PN0AZ70S","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.","https:\u002F\u002Fgithub.com\u002Fpjherron\u002Fhypoc\u002Fblob\u002Fmain\u002Fhypoc\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[]]