[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DHMAMR8YA6TBFZ3EV82BDK":3,"skill-same:01M7DHMAMR8YA6TBFZ3EV82BDK":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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7DHMAMR8YA6TBFZ3EV82BDK","critique",null,"Run a 5-dimension expert design review on any HTML artifact in the\nproject — Philosophy \u002F Visual hierarchy \u002F Detail \u002F Functionality \u002F\nInnovation, each scored 0–10. Outputs a single self-contained HTML\nreport with a radar chart, evidence-backed scores, and three lists:\nKeep \u002F Fix \u002F Quick-wins. Use when the brief asks for a \"design\nreview\", \"design critique\", \"5 维度评审\", \"design audit\", or \"what's\nwrong with my design\".","andremolnar\u002Fopen-open-design","andremolnar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F919644?v=4","01M7DHE1X4QH6SJBHR92VG5N84","01M7DHE1XRHK1WQV34AM9M328E",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fcritique\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: critique\ndescription: |\n  Run a 5-dimension expert design review on any HTML artifact in the\n  project — Philosophy \u002F Visual hierarchy \u002F Detail \u002F Functionality \u002F\n  Innovation, each scored 0–10. Outputs a single self-contained HTML\n  report with a radar chart, evidence-backed scores, and three lists:\n  Keep \u002F Fix \u002F Quick-wins. Use when the brief asks for a \"design\n  review\", \"design critique\", \"5 维度评审\", \"design audit\", or \"what's\n  wrong with my design\".\ntriggers:\n  - \"critique\"\n  - \"design review\"\n  - \"design audit\"\n  - \"5 维度评审\"\n  - \"5-dim review\"\n  - \"audit my design\"\n  - \"review my deck\"\n  - \"review my landing page\"\n  - \"评审\"\n  - \"复盘\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: design\n  upstream: \"https:\u002F\u002Fgithub.com\u002Falchaincyf\u002Fhuashu-design\"\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: false\n  example_prompt: \"Run a 5-dimension critique on the magazine-web-ppt deck I just generated — score philosophy \u002F hierarchy \u002F detail \u002F function \u002F innovation, give me Keep \u002F Fix \u002F Quick-wins.\"\n---\n\n# Critique Skill · 5 维度专家评审\n\nProduce a single-file HTML \"design review report\" that scores any\nartifact across 5 dimensions and proposes actionable fixes. Inspired by\nthe *huashu-design* expert-critique flow.\n\n## When to use\n\n- After the agent (or user) generates an artifact (deck \u002F prototype \u002F\n  landing page) and the user asks \"what's wrong with this?\" or\n  \"review this\"\n- As a self-check loop the agent can run on its own output **before**\n  emitting it\n- For comparing two variants of the same design\n\n## What you produce\n\nA single self-contained `\u003Cartifact type=\"text\u002Fhtml\">` review report\nincluding:\n\n1. **Header** — what artifact was reviewed, date, reviewer (\"OD ·\n   Critique skill\"), 1-line verdict\n2. **Radar chart** (inline SVG, no library) showing the 5 scores\n3. **Five dimension cards**, each with:\n   - Score 0–10 (with band: 0–4 *Broken* · 5–6 *Functional* · 7–8 *Strong*\n     · 9–10 *Exceptional*)\n   - 1-paragraph evidence (cite specific elements \u002F files \u002F lines)\n   - One Keep \u002F Fix \u002F Quick-win bullet\n4. **Combined action lists** at the bottom:\n   - **Keep** — what's working, don't touch\n   - **Fix** — P0 \u002F P1 issues that are visually expensive\n   - **Quick wins** — 5–15 minute tweaks with disproportionate impact\n\n## The 5 dimensions\n\n> Each dimension is independent — a deck can be 9\u002F10 on Innovation but\n> 4\u002F10 on Hierarchy and the report should say so plainly. Don't average\n> away interesting failures.\n\n### 1. Philosophy consistency · 哲学一致性\n\n> Does the artifact pick a clear *direction* and stick to it through\n> every micro-decision (chrome \u002F kicker \u002F spacing \u002F accent)?\n\n**Evidence to look for:**\n- Is there one declared design direction (e.g. Monocle \u002F WIRED \u002F\n  Kinfolk) or is it three styles in a trench coat?\n- Does the chrome \u002F kicker vocabulary stay in one register, or does\n  page 3 say \"Vol.04 · Spring\" and page 7 say \"BUT WAIT 🔥\"?\n- Are accent \u002F serif \u002F mono used by the same rule throughout?\n\n**0–4** Three styles fighting each other. **5–6** One direction but\nhalf the elements drift. **7–8** Coherent, occasional drift on edge\npages. **9–10** Every element argues for the same thesis.\n\n### 2. Visual hierarchy · 视觉层级\n\n> Can a stranger figure out what to read first, second, third — without\n> being told?\n\n**Evidence to look for:**\n- Is the largest type clearly the most important thing on each page?\n- Do mono \u002F serif \u002F sans roles match the information's *role* (meta \u002F\n  body \u002F display)?\n- Lots of \"loud\" elements competing? Or a clear primary + secondary +\n  tertiary tier?\n\n**0–4** Everything shouts. **5–6** Hierarchy works on hero pages but\nbreaks on body. **7–8** Clear tiers, occasional collision. **9–10** Eye\nmoves with zero friction.\n\n### 3. Detail execution · 细节执行\n\n> The 90\u002F10 stuff — alignment, leading, kerning at large sizes, image\n> framing, foot\u002Fchrome polish, edge-case spacing.\n\n**Evidence to look for:**\n- Big-stat pages: does the number sit on a baseline, or float?\n- Left\u002Fright column tops aligned in `grid-2-7-5`?\n- `frame-img` + caption proportions consistent across pages?\n- Mono labels: same letter-spacing? same uppercase rule?\n- Any orphaned `\u003Cbr>` causing 1-character lines?\n\n**0–4** Visible tape and string. **5–6** Most pages clean, 1–2\nragged. **7–8** Polished, expert eye finds 2–3 misses. **9–10**\nMagazine-grade — the kind of detail that makes printed-by-hand\ntypographers nod.\n\n### 4. Functionality · 功能性\n\n> Does the artifact *work* for its intended use? Click targets, nav,\n> readability at presentation distance, copy-paste-ability for code\n> blocks, mobile fallback if relevant.\n\n**Evidence to look for:**\n- Deck: keyboard \u002F wheel \u002F touch nav all working? Iframe scroll\n  fallback?\n- Landing: CTA above the fold? Phone number tappable on mobile?\n- Runbook: code blocks copyable, mono font, no smart quotes?\n- Critical info readable from 4m away (large screen presentation)?\n\n**0–4** Visually fine but doesn't accomplish its job. **5–6** Core\nflow works, edge cases broken. **7–8** Robust through normal use.\n**9–10** Defensively engineered — handles iframe \u002F fullscreen \u002F paste\n\u002F print without flinching.\n\n### 5. Innovation · 创新性\n\n> Does this push past the median? Is there one element that makes\n> people lean in?\n\n**Evidence to look for:**\n- One *unexpected* layout \u002F motion \u002F typographic move that wasn't\n  required?\n- Or 100% safe — could be any deck\u002Flanding from any agency?\n- Is the innovation *earned* (matches direction) or grafted on\n  (random WebGL on a Kinfolk slow-living deck)?\n\n**0–4** Generic AI-slop median. **5–6** Competent and unmemorable.\n**7–8** One memorable moment, the rest solid. **9–10** Multiple\nmoves you'd steal — but each one obviously serves the thesis.\n\n## Scoring discipline (read before you score)\n\n- **Always cite evidence** — \"scored 4 because hero page mixes\n  Playfair display with Inter sans on the same line\" beats \"feels\n  inconsistent\". Numbers without evidence get rejected.\n- **Don't average up** — if Hierarchy is 5 because page 3 is broken,\n  don't bump to 7 because pages 1 and 2 are fine. The score is the\n  *worst sustained band*.\n- **Don't grade-inflate** — a 7 means *strong*, not *acceptable*. If\n  every score is 7+, you're not reviewing critically.\n- **Innovation is allowed to be low** — 5\u002F10 is fine for production\n  deliverables. Don't punish *appropriate* conservatism.\n\n## Workflow\n\n### Step 1 — Acquire the artifact\n\nThree modes:\n\n1. **Project file** — user said \"review the index.html I just made\":\n   open it from the project folder.\n2. **Pasted HTML** — user pasted code in the chat: read it from the\n   message.\n3. **Generated by you in this turn** — you just emitted an artifact\n   above and want to self-critique: re-read your own `\u003Cartifact>`.\n\nIf multiple HTML files exist, ask which one (don't review all).\n\n### Step 2 — Read enough to score\n\nSkim the entire `\u003Cstyle>`, then read 6–8 representative content\nblocks. **Do not score from frontmatter alone.** The score depends on\n*executed* design, not declared intent.\n\n### Step 3 — Score with evidence\n\nFor each of the 5 dimensions, write the score and a 30–80 word\nevidence paragraph that names specific elements. Use line numbers,\nclass names, page numbers.\n\nExample:\n```\nDimension: Detail execution\nScore: 6 \u002F 10\nEvidence: Stat-cards on page 3 align cleanly (grid-6, 3×2), but on\npage 8 the right column foot sits 2vh higher than the left because\n.callout has 3vh top margin while the figure doesn't. Image captions\nuse mono on page 5 but sans on page 7 — pick one.\n```\n\n### Step 4 — Build the action lists\n\nAggregate the 5 evidence paragraphs into:\n\n- **Keep** (3–5 bullets) — concrete things working that the user must\n  not break in the next iteration. Cite by class \u002F page \u002F element.\n- **Fix** (3–6 bullets) — must-do, ordered by *visual cost saved per\n  minute spent*. Each bullet ≤ 1 sentence.\n- **Quick wins** (3–5 bullets) — 5–15 minutes each, high\n  signal-to-noise (e.g. \"swap `display:flex` for `grid` on page 4 to\n  fix the column drift\").\n\n### Step 5 — Emit the report HTML\n\nBuild a single file:\n\n- Header: artifact name + reviewer credit + date\n- Big radar chart (SVG)\n- 5 dimension cards in a 1-column or 2-column grid\n- Three action lists at the bottom with checkbox affordance\n\nUse the active DESIGN.md tokens if one exists; otherwise default to a\nneutral light theme (off-white background, near-black text, one accent\nfor radar fill).\n\n## Output contract\n\n```\n\u003Cartifact identifier=\"critique-\u003Cartifact-slug>\" type=\"text\u002Fhtml\" title=\"Critique · \u003CArtifact Title>\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact (\"Reviewed X across 5 dimensions, see\nreport below.\") and **stop after `\u003C\u002Fartifact>`** — do not paraphrase\nthe report in chat; the user will read the artifact.\n\n## Hard rules\n\n- **5 scores, every time** — partial reports (e.g. only 3 dimensions)\n  are not allowed.\n- **Evidence per score** — no \"feels off\" \u002F \"needs work\". If you\n  can't cite an element, the score is not justified.\n- **Don't grade-inflate** — overall mean above 8 is suspicious; check\n  yourself.\n- **Don't review your own artifact in the same turn** — the user\n  needs to see it first. Self-critique only on explicit request\n  (\"now critique what you just made\").\n- **Single-file HTML only** — no external CSS\u002FJS. Inline everything.\n- **Radar chart is mandatory** — gives the report a recognizable\n  silhouette and lets the user spot weak axes at a glance.\n","# Critique Skill · 5 维度专家评审\n\nProduce a single-file HTML \"design review report\" that scores any\nartifact across 5 dimensions and proposes actionable fixes. Inspired by\nthe *huashu-design* expert-critique flow.\n\n## When to use\n\n- After the agent (or user) generates an artifact (deck \u002F prototype \u002F\n  landing page) and the user asks \"what's wrong with this?\" or\n  \"review this\"\n- As a self-check loop the agent can run on its own output **before**\n  emitting it\n- For comparing two variants of the same design\n\n## What you produce\n\nA single self-contained `\u003Cartifact type=\"text\u002Fhtml\">` review report\nincluding:\n\n1. **Header** — what artifact was reviewed, date, reviewer (\"OD ·\n   Critique skill\"), 1-line verdict\n2. **Radar chart** (inline SVG, no library) showing the 5 scores\n3. **Five dimension cards**, each with:\n   - Score 0–10 (with band: 0–4 *Broken* · 5–6 *Functional* · 7–8 *Strong*\n     · 9–10 *Exceptional*)\n   - 1-paragraph evidence (cite specific elements \u002F files \u002F lines)\n   - One Keep \u002F Fix \u002F Quick-win bullet\n4. **Combined action lists** at the bottom:\n   - **Keep** — what's working, don't touch\n   - **Fix** — P0 \u002F P1 issues that are visually expensive\n   - **Quick wins** — 5–15 minute tweaks with disproportionate impact\n\n## The 5 dimensions\n\n> Each dimension is independent — a deck can be 9\u002F10 on Innovation but\n> 4\u002F10 on Hierarchy and the report should say so plainly. Don't average\n> away interesting failures.\n\n### 1. Philosophy consistency · 哲学一致性\n\n> Does the artifact pick a clear *direction* and stick to it through\n> every micro-decision (chrome \u002F kicker \u002F spacing \u002F accent)?\n\n**Evidence to look for:**\n- Is there one declared design direction (e.g. Monocle \u002F WIRED \u002F\n  Kinfolk) or is it three styles in a trench coat?\n- Does the chrome \u002F kicker vocabulary stay in one register, or does\n  page 3 say \"Vol.04 · Spring\" and page 7 say \"BUT WAIT 🔥\"?\n- Are accent \u002F serif \u002F mono used by the same rule throughout?\n\n**0–4** Three styles fighting each other. **5–6** One direction but\nhalf the elements drift. **7–8** Coherent, occasional drift on edge\npages. **9–10** Every element argues for the same thesis.\n\n### 2. Visual hierarchy · 视觉层级\n\n> Can a stranger figure out what to read first, second, third — without\n> being told?\n\n**Evidence to look for:**\n- Is the largest type clearly the most important thing on each page?\n- Do mono \u002F serif \u002F sans roles match the information's *role* (meta \u002F\n  body \u002F display)?\n- Lots of \"loud\" elements competing? Or a clear primary + secondary +\n  tertiary tier?\n\n**0–4** Everything shouts. **5–6** Hierarchy works on hero pages but\nbreaks on body. **7–8** Clear tiers, occasional collision. **9–10** Eye\nmoves with zero friction.\n\n### 3. Detail execution · 细节执行\n\n> The 90\u002F10 stuff — alignment, leading, kerning at large sizes, image\n> framing, foot\u002Fchrome polish, edge-case spacing.\n\n**Evidence to look for:**\n- Big-stat pages: does the number sit on a baseline, or float?\n- Left\u002Fright column tops aligned in `grid-2-7-5`?\n- `frame-img` + caption proportions consistent across pages?\n- Mono labels: same letter-spacing? same uppercase rule?\n- Any orphaned `\u003Cbr>` causing 1-character lines?\n\n**0–4** Visible tape and string. **5–6** Most pages clean, 1–2\nragged. **7–8** Polished, expert eye finds 2–3 misses. **9–10**\nMagazine-grade — the kind of detail that makes printed-by-hand\ntypographers nod.\n\n### 4. Functionality · 功能性\n\n> Does the artifact *work* for its intended use? Click targets, nav,\n> readability at presentation distance, copy-paste-ability for code\n> blocks, mobile fallback if relevant.\n\n**Evidence to look for:**\n- Deck: keyboard \u002F wheel \u002F touch nav all working? Iframe scroll\n  fallback?\n- Landing: CTA above the fold? Phone number tappable on mobile?\n- Runbook: code blocks copyable, mono font, no smart quotes?\n- Critical info readable from 4m away (large screen presentation)?\n\n**0–4** Visually fine but doesn't accomplish its job. **5–6** Core\nflow works, edge cases broken. **7–8** Robust through normal use.\n**9–10** Defensively engineered — handles iframe \u002F fullscreen \u002F paste\n\u002F print without flinching.\n\n### 5. Innovation · 创新性\n\n> Does this push past the median? Is there one element that makes\n> people lean in?\n\n**Evidence to look for:**\n- One *unexpected* layout \u002F motion \u002F typographic move that wasn't\n  required?\n- Or 100% safe — could be any deck\u002Flanding from any agency?\n- Is the innovation *earned* (matches direction) or grafted on\n  (random WebGL on a Kinfolk slow-living deck)?\n\n**0–4** Generic AI-slop median. **5–6** Competent and unmemorable.\n**7–8** One memorable moment, the rest solid. **9–10** Multiple\nmoves you'd steal — but each one obviously serves the thesis.\n\n## Scoring discipline (read before you score)\n\n- **Always cite evidence** — \"scored 4 because hero page mixes\n  Playfair display with Inter sans on the same line\" beats \"feels\n  inconsistent\". Numbers without evidence get rejected.\n- **Don't average up** — if Hierarchy is 5 because page 3 is broken,\n  don't bump to 7 because pages 1 and 2 are fine. The score is the\n  *worst sustained band*.\n- **Don't grade-inflate** — a 7 means *strong*, not *acceptable*. If\n  every score is 7+, you're not reviewing critically.\n- **Innovation is allowed to be low** — 5\u002F10 is fine for production\n  deliverables. Don't punish *appropriate* conservatism.\n\n## Workflow\n\n### Step 1 — Acquire the artifact\n\nThree modes:\n\n1. **Project file** — user said \"review the index.html I just made\":\n   open it from the project folder.\n2. **Pasted HTML** — user pasted code in the chat: read it from the\n   message.\n3. **Generated by you in this turn** — you just emitted an artifact\n   above and want to self-critique: re-read your own `\u003Cartifact>`.\n\nIf multiple HTML files exist, ask which one (don't review all).\n\n### Step 2 — Read enough to score\n\nSkim the entire `\u003Cstyle>`, then read 6–8 representative content\nblocks. **Do not score from frontmatter alone.** The score depends on\n*executed* design, not declared intent.\n\n### Step 3 — Score with evidence\n\nFor each of the 5 dimensions, write the score and a 30–80 word\nevidence paragraph that names specific elements. Use line numbers,\nclass names, page numbers.\n\nExample:\n```\nDimension: Detail execution\nScore: 6 \u002F 10\nEvidence: Stat-cards on page 3 align cleanly (grid-6, 3×2), but on\npage 8 the right column foot sits 2vh higher than the left because\n.callout has 3vh top margin while the figure doesn't. Image captions\nuse mono on page 5 but sans on page 7 — pick one.\n```\n\n### Step 4 — Build the action lists\n\nAggregate the 5 evidence paragraphs into:\n\n- **Keep** (3–5 bullets) — concrete things working that the user must\n  not break in the next iteration. Cite by class \u002F page \u002F element.\n- **Fix** (3–6 bullets) — must-do, ordered by *visual cost saved per\n  minute spent*. Each bullet ≤ 1 sentence.\n- **Quick wins** (3–5 bullets) — 5–15 minutes each, high\n  signal-to-noise (e.g. \"swap `display:flex` for `grid` on page 4 to\n  fix the column drift\").\n\n### Step 5 — Emit the report HTML\n\nBuild a single file:\n\n- Header: artifact name + reviewer credit + date\n- Big radar chart (SVG)\n- 5 dimension cards in a 1-column or 2-column grid\n- Three action lists at the bottom with checkbox affordance\n\nUse the active DESIGN.md tokens if one exists; otherwise default to a\nneutral light theme (off-white background, near-black text, one accent\nfor radar fill).\n\n## Output contract\n\n```\n\u003Cartifact identifier=\"critique-\u003Cartifact-slug>\" type=\"text\u002Fhtml\" title=\"Critique · \u003CArtifact Title>\">\n\u003C!doctype html>\n\u003Chtml>...\u003C\u002Fhtml>\n\u003C\u002Fartifact>\n```\n\nOne sentence before the artifact (\"Reviewed X across 5 dimensions, see\nreport below.\") and **stop after `\u003C\u002Fartifact>`** — do not paraphrase\nthe report in chat; the user will read the artifact.\n\n## Hard rules\n\n- **5 scores, every time** — partial reports (e.g. only 3 dimensions)\n  are not allowed.\n- **Evidence per score** — no \"feels off\" \u002F \"needs work\". If you\n  can't cite an element, the score is not justified.\n- **Don't grade-inflate** — overall mean above 8 is suspicious; check\n  yourself.\n- **Don't review your own artifact in the same turn** — the user\n  needs to see it first. Self-critique only on explicit request\n  (\"now critique what you just made\").\n- **Single-file HTML only** — no external CSS\u002FJS. Inline everything.\n- **Radar chart is mandatory** — gives the report a recognizable\n  silhouette and lets the user spot weak axes at a glance.\n",{"od":23,"name":5,"triggers":33,"description":43},{"mode":24,"preview":25,"platform":28,"scenario":29,"upstream":30,"design_system":31,"example_prompt":32},"prototype",{"type":26,"entry":27},"html","index.html","desktop","design","https:\u002F\u002Fgithub.com\u002Falchaincyf\u002Fhuashu-design",{"requires":19},"Run a 5-dimension critique on the magazine-web-ppt deck I just generated — score philosophy \u002F hierarchy \u002F detail \u002F function \u002F innovation, give me Keep \u002F Fix \u002F Quick-wins.",[5,34,35,36,37,38,39,40,41,42],"design review","design audit","5 维度评审","5-dim review","audit my design","review my deck","review my landing page","评审","复盘","Run a 5-dimension expert design review on any HTML artifact in the\nproject — Philosophy \u002F Visual hierarchy \u002F Detail \u002F Functionality \u002F\nInnovation, each scored 0–10. Outputs a single self-contained HTML\nreport with a radar chart, evidence-backed scores, and three lists:\nKeep \u002F Fix \u002F Quick-wins. Use when the brief asks for a \"design\nreview\", \"design critique\", \"5 维度评审\", \"design audit\", or \"what's\nwrong with my design\".\n","main","3a6721b94dec7506e324023f2855495c9c54d0d2","design-templates\u002Fcritique",0,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fandremolnar","2026-10-30 01:33:11",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add andremolnar\u002Fopen-open-design --skill critique",{"tool":58,"command":59},"bunx","bunx skills add andremolnar\u002Fopen-open-design --skill critique",{"tool":61,"command":62},"pnpm","pnpm dlx skills add andremolnar\u002Fopen-open-design --skill critique","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fcritique\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"example.html","REFERENCE","参考文档",27012,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fcritique\u002Fexample.html",[73,80,87,94,101,110],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7DMPDFNBD52ZP0GNY046Z2A","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7DMPC4JJ8ENX7VWTMP38Y9C","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7DMP9J5BX307VWVD67J0BBM","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7DMP7GNYTFXGK9RDZ2X723P","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7DMP2WHMNKM0P5BXRYAG8D1","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7DMP0GVJQ37CGXYQDD20VWS","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]