[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXB1ZF46PRZBHDEQRBV22H":3,"skill-same:01M7EXB1ZF46PRZBHDEQRBV22H":97},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7EXB1ZF46PRZBHDEQRBV22H","md-review",null,"Converts a markdown PR writeup or code review (one with ```diff fenced blocks and severity-tagged > [!BLOCKER]\u002F[!MAJOR]\u002F[!MINOR]\u002F[!NIT] callouts) into a single-file 2-column HTML review — unified-diff on the left, severity-tagged annotation cards on the right, top jump-nav listing every finding, mandatory named reviewer footer. Triggers when the markdown-html-orchestrator classifies an input as REVIEW, or when invoked directly via \u002Fcs:md-review. Refuses without explicit --reviewer (a code review must name a human), refuses if no diff hunks present (route to md-document instead), and refuses to encode severity in color only (every badge ships color + icon + aria-label per WCAG 1.4.1). Use after orchestrator routing.","ibada0410\u002FCLAUDE-SKILLS","ibada0410","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237597776?v=4","01M7EQWAZNCZV6Y4AGVBXWV5CD","Ibad Ahmed","01M7EQWB08BHXD7VT182EBQDCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: md-review\ndescription: Converts a markdown PR writeup or code review (one with ```diff fenced blocks and severity-tagged > [!BLOCKER]\u002F[!MAJOR]\u002F[!MINOR]\u002F[!NIT] callouts) into a single-file 2-column HTML review — unified-diff on the left, severity-tagged annotation cards on the right, top jump-nav listing every finding, mandatory named reviewer footer. Triggers when the markdown-html-orchestrator classifies an input as REVIEW, or when invoked directly via \u002Fcs:md-review. Refuses without explicit --reviewer (a code review must name a human), refuses if no diff hunks present (route to md-document instead), and refuses to encode severity in color only (every badge ships color + icon + aria-label per WCAG 1.4.1). Use after orchestrator routing.\nversion: 2.10.2\nauthor: Alireza Rezvani\nlicense: MIT\ntags: [markdown, html, code-review, diff, severity, annotations, single-file, design-system, wcag-1.4.1]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# md-review — Code-review markdown → 2-column HTML\n\nThe code-review converter from Tier 2 of Shihipar's essay (\"Code Review and PR Writeups\"). Takes a markdown PR writeup with diff blocks + severity callouts and produces a single-file HTML review with a jump-nav, 2-column diff + annotation layout, and a named reviewer footer.\n\nThree stdlib tools pipeline together:\n\n```\ndiff_parser.py  →  annotation_extractor.py  →  review_html_renderer.py\n   (md → diff hunks)   (md → severity-tagged    (hunks + annotations\n                        annotations attached     + tokens → 2-col HTML)\n                        to nearest hunk)\n```\n\n## When to invoke\n\n| Symptom | Action |\n|---|---|\n| `markdown-html-orchestrator` routes input as REVIEW | Invoke this skill |\n| User runs `\u002Fcs:md-review \u003Cpath>.md` directly | Invoke this skill |\n| Input contains ` ```diff ` fenced blocks + `> [!MAJOR]`\u002F`> [!BLOCKER]`\u002Fetc. callouts | Invoke this skill |\n| Input is a long-form spec \u002F report (no diff blocks) | Route to `md-document` instead |\n| Input is a slide deck | Route to `md-slides` instead |\n| Input \u003C 100 lines | Refuse (Shihipar threshold) |\n| Design-system not onboarded | Refuse; surface `\u002Fcs:design-system` |\n\n## Pipeline\n\n```bash\n# 1. Parse markdown → diff hunks JSON\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Fdiff_parser.py \\\n    --input \u003Cpath>.md --output hunks.json\n\n# 2. Extract severity-tagged annotations, attach to nearest preceding hunk\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Fannotation_extractor.py \\\n    --input \u003Cpath>.md --diff-blocks hunks.json --output annotations.json\n\n# 3. Render 2-col HTML (--reviewer is mandatory — refuses without)\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Freview_html_renderer.py \\\n    --diff-blocks hunks.json --annotations annotations.json \\\n    --reviewer \"Jane Doe\" --title \"PR #123: Add retry logic\" \\\n    --output review.html\n```\n\n## What gets rendered\n\n- **Top jump-nav** — every annotation with severity badge + 80-char preview + jump link; severity counts in the heading (\"3 BLOCKER · 2 MAJOR · 1 NIT\")\n- **2-column hunk rows** — unified diff on the left (per-line old\u002Fnew line numbers, +\u002F− marks, addition\u002Fdeletion background tint from design-system tokens), annotation cards on the right (color + icon + aria-label per WCAG 1.4.1)\n- **Approval bar** — if `LGTM` markers are present and no severity annotations, a success-tinted \"LGTM — no findings flagged\" bar\n- **General comments** — annotations not attached to any hunk render at the bottom in their own section\n- **Reviewer footer** — mandatory; refuses to render without `--reviewer`\n- **Responsive** — 2-col collapses to stacked on viewports \u003C 900px\n\n## Hard rules\n\n1. **`--reviewer` is mandatory.** A code review must name a human reviewer. Refuses with exit 3 otherwise. Mirrors research-ops's \"named owner\" discipline.\n2. **Refuses if no hunks present.** No `--- a\u002Ffile` + `@@ ... @@` blocks means this isn't a code review — refuses with exit 4 and recommends `md-document`.\n3. **Refuses input \u003C 100 lines.** Markdown wins below the threshold (Shihipar).\n4. **Refuses without onboarding.** Same gate as every converter.\n5. **Severity is never color-only.** Each badge ships color + icon + `aria-label` + text. WCAG 1.4.1 enforced at the renderer level.\n6. **Single-file output.** All CSS inline. Only external is Google Fonts CSS. No Prism in md-review (diff coloring conflicts with syntax highlighting).\n7. **Custom severity convention.** `--severity-convention \"critical,important,suggestion,nit\"` swaps tier names; position 0 is most severe. Default is BLOCKER \u002F MAJOR \u002F MINOR \u002F NIT (Google Code Review Developer Guide).\n\n## Forcing-question library (Matt Pocock grill discipline)\n\n1. **Who is the named reviewer?** Recommended: the user signing off on the review. Canon: research-ops named-owner pattern; *SWE at Google* ch. 9.\n2. **Which severity convention applies — default (BLOCKER\u002FMAJOR\u002FMINOR\u002FNIT) or custom?** Recommended: default unless your team has a documented alternative. Canon: Google *Code Review Developer Guide*.\n3. **Are annotations anchored to specific hunks, or are some general?** Recommended: anchor everything you can; general goes to the unanchored section. Canon: *SWE at Google* ch. 9 — \"Comments must reference a specific line\".\n4. **What's the PR title for the `\u003Ctitle>` and header?** Recommended: the actual PR \u002F commit title. Canon: docs-as-context-for-readers.\n5. **Should `LGTM` markers ship as the approval bar?** Recommended: yes if there are no severity annotations; otherwise the findings take precedence.\n\n## Distinct from\n\n- **`md-document`** — that converter renders prose + tables + code + callouts. This one renders diff hunks + margin annotations.\n- **`md-slides`** — that converter splits on `---` boundaries. This one is a single-page artifact.\n- **GitHub PR comments** — those are a thread. This is a single-author snapshot artifact.\n\n## Output artifact\n\n`{default_output_dir}\u002Freview-{slug}.html` (path resolved by orchestrator's `output_path_resolver.py`; collision suffix `-2`, `-3`, … by default).\n\n## References\n\n- Shihipar — *Claude Code HTML output* (Medium, 2026), Tier 2 use case\n- *Software Engineering at Google* (Manshreck & Wright, O'Reilly 2020), ch. 9 \"Code Review\"\n- Google *Code Review Developer Guide* — severity convention source\n- WCAG 2.2 §1.4.1 — color-not-sole-signal enforcement\n- See `references\u002F` for full citations (diff_rendering_canon, severity_coding, pr_annotation_ux)\n","# md-review — Code-review markdown → 2-column HTML\n\nThe code-review converter from Tier 2 of Shihipar's essay (\"Code Review and PR Writeups\"). Takes a markdown PR writeup with diff blocks + severity callouts and produces a single-file HTML review with a jump-nav, 2-column diff + annotation layout, and a named reviewer footer.\n\nThree stdlib tools pipeline together:\n\n```\ndiff_parser.py  →  annotation_extractor.py  →  review_html_renderer.py\n   (md → diff hunks)   (md → severity-tagged    (hunks + annotations\n                        annotations attached     + tokens → 2-col HTML)\n                        to nearest hunk)\n```\n\n## When to invoke\n\n| Symptom | Action |\n|---|---|\n| `markdown-html-orchestrator` routes input as REVIEW | Invoke this skill |\n| User runs `\u002Fcs:md-review \u003Cpath>.md` directly | Invoke this skill |\n| Input contains ` ```diff ` fenced blocks + `> [!MAJOR]`\u002F`> [!BLOCKER]`\u002Fetc. callouts | Invoke this skill |\n| Input is a long-form spec \u002F report (no diff blocks) | Route to `md-document` instead |\n| Input is a slide deck | Route to `md-slides` instead |\n| Input \u003C 100 lines | Refuse (Shihipar threshold) |\n| Design-system not onboarded | Refuse; surface `\u002Fcs:design-system` |\n\n## Pipeline\n\n```bash\n# 1. Parse markdown → diff hunks JSON\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Fdiff_parser.py \\\n    --input \u003Cpath>.md --output hunks.json\n\n# 2. Extract severity-tagged annotations, attach to nearest preceding hunk\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Fannotation_extractor.py \\\n    --input \u003Cpath>.md --diff-blocks hunks.json --output annotations.json\n\n# 3. Render 2-col HTML (--reviewer is mandatory — refuses without)\npython3 markdown-html\u002Fskills\u002Fmd-review\u002Fscripts\u002Freview_html_renderer.py \\\n    --diff-blocks hunks.json --annotations annotations.json \\\n    --reviewer \"Jane Doe\" --title \"PR #123: Add retry logic\" \\\n    --output review.html\n```\n\n## What gets rendered\n\n- **Top jump-nav** — every annotation with severity badge + 80-char preview + jump link; severity counts in the heading (\"3 BLOCKER · 2 MAJOR · 1 NIT\")\n- **2-column hunk rows** — unified diff on the left (per-line old\u002Fnew line numbers, +\u002F− marks, addition\u002Fdeletion background tint from design-system tokens), annotation cards on the right (color + icon + aria-label per WCAG 1.4.1)\n- **Approval bar** — if `LGTM` markers are present and no severity annotations, a success-tinted \"LGTM — no findings flagged\" bar\n- **General comments** — annotations not attached to any hunk render at the bottom in their own section\n- **Reviewer footer** — mandatory; refuses to render without `--reviewer`\n- **Responsive** — 2-col collapses to stacked on viewports \u003C 900px\n\n## Hard rules\n\n1. **`--reviewer` is mandatory.** A code review must name a human reviewer. Refuses with exit 3 otherwise. Mirrors research-ops's \"named owner\" discipline.\n2. **Refuses if no hunks present.** No `--- a\u002Ffile` + `@@ ... @@` blocks means this isn't a code review — refuses with exit 4 and recommends `md-document`.\n3. **Refuses input \u003C 100 lines.** Markdown wins below the threshold (Shihipar).\n4. **Refuses without onboarding.** Same gate as every converter.\n5. **Severity is never color-only.** Each badge ships color + icon + `aria-label` + text. WCAG 1.4.1 enforced at the renderer level.\n6. **Single-file output.** All CSS inline. Only external is Google Fonts CSS. No Prism in md-review (diff coloring conflicts with syntax highlighting).\n7. **Custom severity convention.** `--severity-convention \"critical,important,suggestion,nit\"` swaps tier names; position 0 is most severe. Default is BLOCKER \u002F MAJOR \u002F MINOR \u002F NIT (Google Code Review Developer Guide).\n\n## Forcing-question library (Matt Pocock grill discipline)\n\n1. **Who is the named reviewer?** Recommended: the user signing off on the review. Canon: research-ops named-owner pattern; *SWE at Google* ch. 9.\n2. **Which severity convention applies — default (BLOCKER\u002FMAJOR\u002FMINOR\u002FNIT) or custom?** Recommended: default unless your team has a documented alternative. Canon: Google *Code Review Developer Guide*.\n3. **Are annotations anchored to specific hunks, or are some general?** Recommended: anchor everything you can; general goes to the unanchored section. Canon: *SWE at Google* ch. 9 — \"Comments must reference a specific line\".\n4. **What's the PR title for the `\u003Ctitle>` and header?** Recommended: the actual PR \u002F commit title. Canon: docs-as-context-for-readers.\n5. **Should `LGTM` markers ship as the approval bar?** Recommended: yes if there are no severity annotations; otherwise the findings take precedence.\n\n## Distinct from\n\n- **`md-document`** — that converter renders prose + tables + code + callouts. This one renders diff hunks + margin annotations.\n- **`md-slides`** — that converter splits on `---` boundaries. This one is a single-page artifact.\n- **GitHub PR comments** — those are a thread. This is a single-author snapshot artifact.\n\n## Output artifact\n\n`{default_output_dir}\u002Freview-{slug}.html` (path resolved by orchestrator's `output_path_resolver.py`; collision suffix `-2`, `-3`, … by default).\n\n## References\n\n- Shihipar — *Claude Code HTML output* (Medium, 2026), Tier 2 use case\n- *Software Engineering at Google* (Manshreck & Wright, O'Reilly 2020), ch. 9 \"Code Review\"\n- Google *Code Review Developer Guide* — severity convention source\n- WCAG 2.2 §1.4.1 — color-not-sole-signal enforcement\n- See `references\u002F` for full citations (diff_rendering_canon, severity_coding, pr_annotation_ux)\n",{"name":5,"tags":24,"author":34,"license":15,"version":35,"description":7,"compatible_tools":36},[25,26,27,28,29,30,31,32,33],"markdown","html","code-review","diff","severity","annotations","single-file","design-system","wcag-1.4.1","Alireza Rezvani","2.10.2",[37,38,39,40,41,42],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","26a049c61e6bda33cca8f5e7c1fcdcd20681221f","Documents-and-Office\u002Fmd-review","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS","https:\u002F\u002Fgithub.com\u002Fibada0410","2026-10-15 17:21:48",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ibada0410\u002FCLAUDE-SKILLS --skill md-review",{"tool":55,"command":56},"bunx","bunx skills add ibada0410\u002FCLAUDE-SKILLS --skill md-review",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ibada0410\u002FCLAUDE-SKILLS --skill md-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002FSKILL.md",true,[63,69,75,79,83,89,93],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Fmd_review_template.html","ASSET","资产文件",4649,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Fassets\u002Fmd_review_template.html",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fdiff_rendering_canon.md","REFERENCE","参考文档",5161,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Freferences\u002Fdiff_rendering_canon.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fpr_annotation_ux.md",5491,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Freferences\u002Fpr_annotation_ux.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fseverity_coding.md",5064,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Freferences\u002Fseverity_coding.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fannotation_extractor.py","SCRIPT","脚本",7761,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Fscripts\u002Fannotation_extractor.py",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fdiff_parser.py",10132,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Fscripts\u002Fdiff_parser.py",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Freview_html_renderer.py",22213,"https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FDocuments-and-Office\u002Fmd-review\u002Fscripts\u002Freview_html_renderer.py",[98,108,116,124,132,140],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"01M7F0YW5WXY39G4W3203E8PHN","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Finternal-comms\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":107},"01M7F0YGDEVB7BCSJX8V91XK15","eu-ai-act-reviewer","Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Feu-ai-act-reviewer\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":107},"01M7F0Y1GYY34HD1WM5EWYB80Z","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Fdiscernment-nudge\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":107},"01M7F0W4SJJY8Z345JZH9901RD","academy-guide","Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: \"how do I\", \"how can I\", \"getting started with\", \"what can Claude do\", \"teach me\", \"learn to use\"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FWriting-Compliance-and-General\u002Facademy-guide\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":107},"01M7F0W0X5YSTSFS77CFA5P5KJ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":107},"01M7F0VV4P1HYHG44P0K48C4Q7","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fibada0410\u002FCLAUDE-SKILLS\u002Fblob\u002Fmain\u002FUI-and-Web-Design\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]