[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYYP2ZYE4T4X7MSVNHKXW8":3,"skill-same:01M6BYYP2ZYE4T4X7MSVNHKXW8":82},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":55},"01M6BYYP2ZYE4T4X7MSVNHKXW8","plannotator-visual-explainer",null,"Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon\u002Fvisual-explainer.","Dyrean\u002Fdotfiles","Dyrean","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86002063?v=4","01M6BYY56KX9D8SKDEN1CYH2K0","Fatih","01M6BYY5AS7V8D6CY4RC20QZHD",0,"MIT","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"plannotator visual explainer","visual explainer","explainer","architecture","pr","architecture diagrams","generate","content","data","visualizations","2026-11-10 10:12:30",false,"---\nname: plannotator-visual-explainer\ndisable-model-invocation: true\ndescription: >\n  Generate self-contained HTML visualizations with Plannotator theming. Use for implementation\n  plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual\n  explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive\n  approach; all other visual content delegates to nicobailon\u002Fvisual-explainer.\n---\n\n# Plannotator Visual Explainer\n\nThree paths depending on content type. Each has its own references and structure.\n\n## Route by content type\n\n**Implementation plan, design doc, or proposal** → Follow the [Plan path](#plan-path). Read `references\u002Fdesign-system.md` and `references\u002Fsvg-patterns.md`. Prescriptive structure.\n\n**PR explainer, diff review, or code change walkthrough** → Follow the [PR path](#pr-path). Read `references\u002Fdesign-system.md` and `references\u002Fpr-components.md`. Prescriptive structure.\n\n**Everything else** (architecture diagrams, data tables, slide decks, project recaps, general visual explanations) → Follow the [Visual explainer path](#visual-explainer-path). Delegates to nicobailon\u002Fvisual-explainer with Plannotator theme tokens.\n\n## Delivery\n\nAlways deliver via Plannotator's annotation UI. Do NOT use `open` or `xdg-open`.\n\nFor any deliverable that uses Mermaid, render every diagram with Mermaid 12 in both the light\nand dark palettes before opening the annotation UI. Rendering is a hard gate: an exception,\nempty SVG, or error output such as `aria-roledescription=\"error\"` or `Syntax error in text`\nmeans the explainer is not deliverable. Fix the diagram or theme configuration and rerun both\npalettes until every SVG passes.\n\nFor zoomable diagram shells, additionally zoom to the maximum and pan to all extremes in both palettes before delivering: the figure caption must stay fully legible throughout (see `references\u002Fdiagram-shell.md`).\n\n**Plans\u002Fproposals** (user should approve\u002Fdeny):\n```bash\nplannotator annotate \u003Cfile> --gate\n```\n\n**Everything else** (informational):\n```bash\nplannotator annotate \u003Cfile>\n```\n\n---\n\n## Plan path\n\nFor implementation plans, design docs, feature specs, migration guides, and proposals.\n\n**Before generating, read:**\n1. `references\u002Fdesign-system.md` — Plannotator theme tokens, typography, component patterns\n2. `references\u002Fsvg-patterns.md` — inline SVG building blocks for architecture diagrams, flowcharts, data flow\n\n**Document structure (in order, pick what fits):**\n\n1. **Header** — eyebrow label (mono, uppercase), title (serif, large), prompt box (the original brief)\n2. **Summary strip** — 3-5 stat cards showing key numbers at a glance (components, endpoints, tables, etc.)\n3. **Milestones \u002F timeline** — vertical timeline showing phases without time estimates. Phases show sequence and dependencies, not duration.\n4. **Architecture \u002F data flow** — inline SVG diagram. Use for 3+ interacting components. Highlighted boxes for new components, dashed arrows for async paths.\n5. **Mockups** — build UI mockups in HTML\u002FCSS directly, not as descriptions\n6. **Key code** — dark-theme code blocks with syntax highlighting. Only architecturally significant interfaces\u002Fschemas — not every function.\n7. **Risks & mitigations** — table with severity badges (HIGH\u002FMED\u002FLOW)\n8. **Open questions** — callout cards with decision owner (\"Decide with: backend team\")\n\nNot every plan needs every section. Skip what doesn't serve the content. Never include time estimates, boilerplate sections, or exhaustive file lists.\n\n**Adapt to the task:** Backend → lead with data flow. Frontend → lead with mockups. Refactoring → lead with before\u002Fafter diagrams. Infrastructure → lead with architecture.\n\n**Quality bar:** The plan answers \"what, why, and how\" within 30 seconds of reading. Whitespace is a feature — one idea per viewport.\n\n---\n\n## PR path\n\nFor PR walkthroughs, diff reviews, code change explainers, and reviewer guides.\n\n**Before generating, read:**\n1. `references\u002Fdesign-system.md` — Plannotator theme tokens, typography, component patterns\n2. `references\u002Fpr-components.md` — diff rendering, review comment bubbles, risk chips, file cards, before\u002Fafter panels\n\n**Document structure (in order, pick what fits):**\n\n1. **Header** — PR title, meta strip (file count, +\u002F- lines, branch, author)\n2. **TL;DR** — bordered card with primary accent left border. 2-3 sentences. Readers who see nothing else should get the gist.\n3. **Why** — motivation and before\u002Fafter comparison (two-column grid)\n4. **File tour** — collapsible cards per file. Each has: file path + badge (NEW\u002FMOD\u002FDEL) + line stats, a \"why\" paragraph, and important diff hunks. High-risk files expanded, safe files collapsed.\n5. **Risk map** — visual chips showing which files need careful review vs. which are mechanical. Three tiers: attention (destructive), medium (warning), safe (success).\n6. **Where to focus** — numbered callout cards. Each names a file\u002Ffunction and describes the concern.\n7. **Test plan** — checkbox-style verification checklist\n8. **Rollout** (if applicable) — phased deployment with feature flags\n\nUse Pierre diffs via CDN for syntax-highlighted inline diffs — see `references\u002Fpr-components.md` for the pattern.\n\n---\n\n## Visual explainer path\n\nFor architecture diagrams, data tables, slide decks, project recaps, comparisons, and any other visual explanation.\n\n**Before generating:**\n\n1. Ensure `visual-explainer` is installed:\n   - Check: `~\u002F.claude\u002Fskills\u002Fvisual-explainer\u002FSKILL.md` or `~\u002F.agents\u002Fskills\u002Fvisual-explainer\u002FSKILL.md`\n   - If not found: `npx skills add nicobailon\u002Fvisual-explainer -g --yes`\n2. Read visual-explainer's `SKILL.md` (workflow, diagram types, anti-slop rules)\n3. Read the relevant visual-explainer references and templates for your content type\n4. Read `references\u002Ftheme-override.md` — Plannotator tokens replacing Nico's palettes\n5. For zoomable Mermaid diagrams with controls and a caption: read `references\u002Fdiagram-shell.md` and copy its shell — do not hand-roll viewport, canvas, or caption markup\n\nFollow visual-explainer's structure, component classes (`.ve-card`, `.kpi-card`, `.pipeline`), and anti-slop rules. Overrides are the color\u002Ftypography layer — Plannotator tokens instead of Nico's custom palettes — plus the zoomable diagram shell in `references\u002Fdiagram-shell.md` when the deliverable has one.\n\n---\n\n## Design philosophy (all paths)\n\n- **Whitespace is a feature.** Generous padding, large section gaps. If cramped, add space — don't shrink text.\n- **One idea per viewport.** Hero section, then diagram, then detail grid — not all crammed together.\n- **Show, don't describe.** A timeline shows sequencing. A diagram shows relationships. A code block shows the interface.\n- **No time estimates.** Timelines show phases and dependencies. Never attach hour\u002Fday estimates.\n","# Plannotator Visual Explainer\n\nThree paths depending on content type. Each has its own references and structure.\n\n## Route by content type\n\n**Implementation plan, design doc, or proposal** → Follow the [Plan path](#plan-path). Read `references\u002Fdesign-system.md` and `references\u002Fsvg-patterns.md`. Prescriptive structure.\n\n**PR explainer, diff review, or code change walkthrough** → Follow the [PR path](#pr-path). Read `references\u002Fdesign-system.md` and `references\u002Fpr-components.md`. Prescriptive structure.\n\n**Everything else** (architecture diagrams, data tables, slide decks, project recaps, general visual explanations) → Follow the [Visual explainer path](#visual-explainer-path). Delegates to nicobailon\u002Fvisual-explainer with Plannotator theme tokens.\n\n## Delivery\n\nAlways deliver via Plannotator's annotation UI. Do NOT use `open` or `xdg-open`.\n\nFor any deliverable that uses Mermaid, render every diagram with Mermaid 12 in both the light\nand dark palettes before opening the annotation UI. Rendering is a hard gate: an exception,\nempty SVG, or error output such as `aria-roledescription=\"error\"` or `Syntax error in text`\nmeans the explainer is not deliverable. Fix the diagram or theme configuration and rerun both\npalettes until every SVG passes.\n\nFor zoomable diagram shells, additionally zoom to the maximum and pan to all extremes in both palettes before delivering: the figure caption must stay fully legible throughout (see `references\u002Fdiagram-shell.md`).\n\n**Plans\u002Fproposals** (user should approve\u002Fdeny):\n```bash\nplannotator annotate \u003Cfile> --gate\n```\n\n**Everything else** (informational):\n```bash\nplannotator annotate \u003Cfile>\n```\n\n---\n\n## Plan path\n\nFor implementation plans, design docs, feature specs, migration guides, and proposals.\n\n**Before generating, read:**\n1. `references\u002Fdesign-system.md` — Plannotator theme tokens, typography, component patterns\n2. `references\u002Fsvg-patterns.md` — inline SVG building blocks for architecture diagrams, flowcharts, data flow\n\n**Document structure (in order, pick what fits):**\n\n1. **Header** — eyebrow label (mono, uppercase), title (serif, large), prompt box (the original brief)\n2. **Summary strip** — 3-5 stat cards showing key numbers at a glance (components, endpoints, tables, etc.)\n3. **Milestones \u002F timeline** — vertical timeline showing phases without time estimates. Phases show sequence and dependencies, not duration.\n4. **Architecture \u002F data flow** — inline SVG diagram. Use for 3+ interacting components. Highlighted boxes for new components, dashed arrows for async paths.\n5. **Mockups** — build UI mockups in HTML\u002FCSS directly, not as descriptions\n6. **Key code** — dark-theme code blocks with syntax highlighting. Only architecturally significant interfaces\u002Fschemas — not every function.\n7. **Risks & mitigations** — table with severity badges (HIGH\u002FMED\u002FLOW)\n8. **Open questions** — callout cards with decision owner (\"Decide with: backend team\")\n\nNot every plan needs every section. Skip what doesn't serve the content. Never include time estimates, boilerplate sections, or exhaustive file lists.\n\n**Adapt to the task:** Backend → lead with data flow. Frontend → lead with mockups. Refactoring → lead with before\u002Fafter diagrams. Infrastructure → lead with architecture.\n\n**Quality bar:** The plan answers \"what, why, and how\" within 30 seconds of reading. Whitespace is a feature — one idea per viewport.\n\n---\n\n## PR path\n\nFor PR walkthroughs, diff reviews, code change explainers, and reviewer guides.\n\n**Before generating, read:**\n1. `references\u002Fdesign-system.md` — Plannotator theme tokens, typography, component patterns\n2. `references\u002Fpr-components.md` — diff rendering, review comment bubbles, risk chips, file cards, before\u002Fafter panels\n\n**Document structure (in order, pick what fits):**\n\n1. **Header** — PR title, meta strip (file count, +\u002F- lines, branch, author)\n2. **TL;DR** — bordered card with primary accent left border. 2-3 sentences. Readers who see nothing else should get the gist.\n3. **Why** — motivation and before\u002Fafter comparison (two-column grid)\n4. **File tour** — collapsible cards per file. Each has: file path + badge (NEW\u002FMOD\u002FDEL) + line stats, a \"why\" paragraph, and important diff hunks. High-risk files expanded, safe files collapsed.\n5. **Risk map** — visual chips showing which files need careful review vs. which are mechanical. Three tiers: attention (destructive), medium (warning), safe (success).\n6. **Where to focus** — numbered callout cards. Each names a file\u002Ffunction and describes the concern.\n7. **Test plan** — checkbox-style verification checklist\n8. **Rollout** (if applicable) — phased deployment with feature flags\n\nUse Pierre diffs via CDN for syntax-highlighted inline diffs — see `references\u002Fpr-components.md` for the pattern.\n\n---\n\n## Visual explainer path\n\nFor architecture diagrams, data tables, slide decks, project recaps, comparisons, and any other visual explanation.\n\n**Before generating:**\n\n1. Ensure `visual-explainer` is installed:\n   - Check: `~\u002F.claude\u002Fskills\u002Fvisual-explainer\u002FSKILL.md` or `~\u002F.agents\u002Fskills\u002Fvisual-explainer\u002FSKILL.md`\n   - If not found: `npx skills add nicobailon\u002Fvisual-explainer -g --yes`\n2. Read visual-explainer's `SKILL.md` (workflow, diagram types, anti-slop rules)\n3. Read the relevant visual-explainer references and templates for your content type\n4. Read `references\u002Ftheme-override.md` — Plannotator tokens replacing Nico's palettes\n5. For zoomable Mermaid diagrams with controls and a caption: read `references\u002Fdiagram-shell.md` and copy its shell — do not hand-roll viewport, canvas, or caption markup\n\nFollow visual-explainer's structure, component classes (`.ve-card`, `.kpi-card`, `.pipeline`), and anti-slop rules. Overrides are the color\u002Ftypography layer — Plannotator tokens instead of Nico's custom palettes — plus the zoomable diagram shell in `references\u002Fdiagram-shell.md` when the deliverable has one.\n\n---\n\n## Design philosophy (all paths)\n\n- **Whitespace is a feature.** Generous padding, large section gaps. If cramped, add space — don't shrink text.\n- **One idea per viewport.** Hero section, then diagram, then detail grid — not all crammed together.\n- **Show, don't describe.** A timeline shows sequencing. A diagram shows relationships. A code block shows the interface.\n- **No time estimates.** Timelines show phases and dependencies. Never attach hour\u002Fday estimates.\n",{"name":5,"description":7,"disable-model-invocation":34},true,"main","e9bed074c277cf363adc3e1774e56de6c8a76281","agents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002FDyrean","canbey.dev","Hello 👋, I'm a Software Engineer based in Turkey!","2026-10-08 00:17:22",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":34},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Dyrean\u002Fdotfiles --skill plannotator-visual-explainer",{"tool":49,"command":50},"bunx","bunx skills add Dyrean\u002Fdotfiles --skill plannotator-visual-explainer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Dyrean\u002Fdotfiles --skill plannotator-visual-explainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002FSKILL.md",[56,62,66,70,74,78],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"README.md","REFERENCE","参考文档",1226,"https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fcaveman-commit\u002FREADME.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdesign-system.md",13200,"https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002Freferences\u002Fdesign-system.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fdiagram-shell.md",4051,"https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002Freferences\u002Fdiagram-shell.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fpr-components.md",15984,"https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002Freferences\u002Fpr-components.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsvg-patterns.md",13518,"https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002Freferences\u002Fsvg-patterns.md",{"path":79,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Ftheme-override.md",7964,"https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-visual-explainer\u002Freferences\u002Ftheme-override.md",[83,103,114,129,150,161],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":99,"publishedAt":29},"01M6BYYXQ82T5RV6TJZWR26VMJ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[89,94],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[100,101,102],"writing for agents","writing","documents",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":29},"01M6BYYTYMTQSSRREPPE6JWGFZ","tech-spec","Write a typed call-stack architecture handoff.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Ftech-spec\u002FSKILL.md",[],[110,111,112,22,113],"tech spec","spec","handoff","stack",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":29},"01M6BYYRSY9SF7RYXP1PCF3DDV","prototype","Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fprototype\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000032","设计师",[116,124,125,126,127,128],"explore","design","state","ui","model",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":138,"publishedAt":29},"01M6BYYM9K2JKD7MRHNS3EMHBV","plannotator-review","Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-review\u002FSKILL.md",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000007","代码审查",[139,140,141,127,142,143,144,145,146,147,148,149],"plannotator review","review","worktree","open","feedback","browser","pull","code review","directory","pull request","code",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":29},"01M6BYYK1J77SBANKAB8DMDASJ","plannotator-last","Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-last\u002FSKILL.md",[],[157,158,142,159,160],"plannotator last","assistant","continue","annotations",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":173,"publishedAt":29},"01M6BYYFNF31KKD1N6FHF6A3PR","plannotator-compound","Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.","https:\u002F\u002Fgithub.com\u002FDyrean\u002Fdotfiles\u002Fblob\u002Fmain\u002Fagents\u002F.agents\u002Fskills\u002Fplannotator-compound\u002FSKILL.md",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":171,"categoryName":172,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000033","数据分析师",[174,149,175,176,27,177,178,179,180,143,181],"plannotator compound","report","produce","taxonomy","plan","archive","analyze","dashboard"]