[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJC6ZCGG3F7MPKD88HBP8D":3,"skill-same:01M6QJC6ZCGG3F7MPKD88HBP8D":98},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":14,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M6QJC6ZCGG3F7MPKD88HBP8D","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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmd-review\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"review","md review","design-system","top","input","present","human","route","aria","opencode","only","markdown-html","code review","orchestrator","reviewer","markdown","code-review","code","cli","design","2026-11-10 10:12:30",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":60,"author":67,"license":15,"version":68,"description":7,"compatible_tools":69},[50,61,51,62,63,64,65,37,66],"html","diff","severity","annotations","single-file","wcag-1.4.1","Alireza Rezvani","2.10.2",[70,71,72,73,44,74],"claude-code","codex-cli","cursor","antigravity","gemini-cli","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fmd-review","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill md-review",{"tool":90,"command":91},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill md-review",{"tool":93,"command":94},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill md-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmd-review\u002FSKILL.md",true,[],[99,129,154,181,206,228],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":55},"01M6QRD07D4TGNDK6VJ4EHF8BV","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\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"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":135,"publishedAt":55},"01M6QRCJ3112VYPA97YG7KGMC2","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\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[136,137,138,139,113,140,141,142,143,144,145,146,147,148,149,150,151,152,153,125],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":55},"01M6QRBN3EHQNJY42RERP7A149","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\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[164,147,165,166,167,168,169,170,149,171,172,75,173,174,175,176,177,178,179,180],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":55},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[188,189,190,191,192,193,194,195,196,149,197,120,198,199,200,201,202,203,204,205],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":55},"01M6QRA5AYC1RBFZ39GTWGS3N8","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\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[212],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},[214,215,216,54,217,166,193,52,218,219,220,221,147,222,119,223,224,225,226,227],"workflow","workflow builder","builder","workflows","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":55},"01M6QR7QMCZESKQA0ERW1E657M","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\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[35,235,236,237,238,239,240,241,242,220,243,244,245,246,247,248,121,249,250,205],"weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]