[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YKMQ93FQCGCCFBTXTSSCV":3,"skill-same:01M79YKMQ93FQCGCCFBTXTSSCV":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},"01M79YKMQ93FQCGCCFBTXTSSCV","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.","Heverton-web\u002Fskill-manager","Heverton-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136394064?v=4","01M79STQDWSTA88J5CA9QR184V","Heverton Eduardo Peres","01M79SX01KSKBZ828C257RAC8P",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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","4c9acccad4644b62896dcb63e794f0d936b35d94","fabrica-de-livros\u002Fagentic\u002Fskills\u002Fmd-review","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FHeverton-web","2026-08-06 09:12:45",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Heverton-web\u002Fskill-manager --skill md-review",{"tool":55,"command":56},"bunx","bunx skills add Heverton-web\u002Fskill-manager --skill md-review",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Heverton-web\u002Fskill-manager --skill md-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\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\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fmd-review\u002Fscripts\u002Freview_html_renderer.py",[98,105,112,119,126,133],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79ZW1HMA4KQ5NQKBNATQWYD","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M79ZVENME42XFYS7F7W7TQYF","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M79ZTQW25Y85KSE58B8YTDR4","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M79ZTJ181TCYK8K995E26VDZ","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M79ZT5Q0B9WNWNQFZRFMK197","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M79ZSS3DTNNTAZYD2CZ9C4Z5","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]