[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QPJ86QMND4F4PNTEWTQVJD":3,"skill-same:01M6QPJ86QMND4F4PNTEWTQVJD":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6QPJ86QMND4F4PNTEWTQVJD","self-eval",null,"Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.","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\u002Fself-eval\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"self","eval","self eval","evaluate","code review","get","across","scoring","task","work session","use","session","work","quality","system","devil","code","assessment","sessions","review","2026-11-10 10:12:30",false,"---\nname: \"self-eval\"\ndescription: \"Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.\"\nlicense: \"MIT\"\n---\n\n# Self-Eval: Honest Work Evaluation\n\nultrathink\n\n**Tier:** STANDARD\n**Category:** Engineering \u002F Quality\n**Dependencies:** None (prompt-only, no external tools required)\n\n## Description\n\nSelf-eval is a Claude Code skill that produces honest, calibrated work evaluations. It replaces the default AI tendency to rate everything 4\u002F5 with a structured two-axis scoring system, mandatory devil's advocate reasoning, and cross-session anti-inflation detection.\n\nThe core insight: AI self-assessment converges to \"everything is a 4\" because a single-axis score conflates task difficulty with execution quality. Self-eval separates these axes, then combines them via a fixed matrix that the model cannot override.\n\n## Features\n\n- **Two-axis scoring** — Independently rates task ambition (Low\u002FMedium\u002FHigh) and execution quality (Poor\u002FAdequate\u002FStrong), then combines via a lookup matrix\n- **Mandatory devil's advocate** — Before finalizing, must argue for both higher AND lower scores, then resolve the tension\n- **Score persistence** — Appends scores to `.self-eval-scores.jsonl` in the working directory, building history across sessions\n- **Anti-inflation detection** — Reads past scores and flags clustering (4+ of last 5 identical)\n- **Matrix-locked scoring** — The composite score comes from the matrix, not from direct selection. Low ambition caps at 2\u002F5 regardless of execution quality\n\n## Usage\n\nAfter completing work in a Claude Code session:\n\n```\n\u002Fself-eval\n```\n\nWith context about what to evaluate:\n\n```\n\u002Fself-eval the authentication refactor we just completed\n```\n\nThe skill reviews the conversation history, identifies what was accomplished, scores it on both axes, runs the devil's advocate check, and appends the result to the score history file.\n\n## Examples\n\n### Example 1: Feature Implementation\n\n```\n\u002Fself-eval added pagination to the user list API\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Added cursor-based pagination to the user list API endpoint\n**Ambition:** Medium — New feature with established patterns, but required careful backwards compatibility\n**Execution:** Strong — All tests pass, handles edge cases, existing clients unaffected\n\n**Devil's Advocate:**\n- Lower: Pagination is well-documented. The pattern was copied from another endpoint with minor changes. Could argue Low ambition.\n- Higher: The backwards-compat requirement made this harder than a greenfield implementation. Had to support both offset and cursor modes.\n- Resolution: Medium ambition holds — the backwards-compat constraint added real complexity beyond copy-paste.\n\n**Score: 4** — Solid execution on meaningful work with real constraints.\n```\n\n### Example 2: Bug Fix\n\n```\n\u002Fself-eval\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Fixed race condition in the checkout flow causing duplicate orders\n**Ambition:** Medium — Required debugging across 3 services to find the root cause\n**Execution:** Adequate — Fix works but the test only covers the exact scenario reported, not the general class of race conditions\n\n**Devil's Advocate:**\n- Lower: The fix was a single line (adding a mutex). Once found, it was trivial.\n- Higher: Finding the root cause across 3 services took real investigation. The mutex placement required understanding the full flow.\n- Resolution: Medium ambition is correct for the investigation, but execution drops to Adequate — a more thorough fix would address the pattern, not just the instance.\n\n**Score: 3** — Good debugging work but the fix is narrow.\n```\n\n---\n\n## What to Evaluate\n\n$ARGUMENTS\n\nIf no arguments provided, review the full conversation history to identify what was accomplished this session. Summarize the work in one sentence before scoring.\n\n## How to Score — Two-Axis Model\n\nScore on two independent axes, then combine using the matrix. Do NOT pick a number first and rationalize it — rate each axis separately, then read the matrix.\n\n### Axis 1: Task Ambition (what was attempted)\n\nRate the difficulty and risk of what was worked on. NOT how well it was done.\n\n- **Low (1)** — Safe, familiar, routine. No real risk of failure. Examples: minor config changes, simple refactors, copy-paste with small modifications, tasks you were confident you'd complete before starting.\n- **Medium (2)** — Meaningful work with novelty or challenge. Partial failure was possible. Examples: new feature implementation, integrating an unfamiliar API, architectural changes, debugging a tricky issue.\n- **High (3)** — Ambitious, unfamiliar, or high-stakes. Real risk of complete failure. Examples: building something from scratch in an unfamiliar domain, complex system redesign, performance-critical optimization, shipping to production under pressure.\n\n**Self-check:** If you were confident of success before starting, ambition is Low or Medium, not High.\n\n### Axis 2: Execution Quality (how well it was done)\n\nRate the quality of the actual output, independent of how ambitious the task was.\n\n- **Poor (1)** — Major failures, incomplete, wrong output, or abandoned mid-task. The deliverable doesn't meet its own stated criteria.\n- **Adequate (2)** — Completed but with gaps, shortcuts, or missing rigor. Did the thing but left obvious improvements on the table.\n- **Strong (3)** — Well-executed, thorough, quality output. No obvious improvements left undone given the scope.\n\n### Composite Score Matrix\n\n|                        | Poor Exec (1) | Adequate Exec (2) | Strong Exec (3) |\n|------------------------|:---:|:---:|:---:|\n| **Low Ambition (1)**   |  1  |  2  |  2  |\n| **Medium Ambition (2)**|  2  |  3  |  4  |\n| **High Ambition (3)**  |  2  |  4  |  5  |\n\n**Read the matrix, don't override it.** The composite is your score. The devil's advocate below can cause you to re-rate an axis — but you cannot directly override the matrix result.\n\nKey properties:\n- Low ambition caps at 2. Safe work done perfectly is still safe work.\n- A 5 requires BOTH high ambition AND strong execution. It should be rare.\n- High ambition + poor execution = 2. Bold failure hurts.\n- The most common honest score for solid work is 3 (medium ambition, adequate execution).\n\n## Devil's Advocate (MANDATORY)\n\nBefore writing your final score, you MUST write all three of these:\n\n1. **Case for LOWER:** Why might this work deserve a lower score? What was easy, what was avoided, what was less ambitious than it appears? Would a skeptical reviewer agree with your axis ratings?\n2. **Case for HIGHER:** Why might this work deserve a higher score? What was genuinely challenging, surprising, or exceeded the original plan?\n3. **Resolution:** If either case reveals you mis-rated an axis, re-rate it and recompute the matrix result. Then state your final score with a 1-2 sentence justification that addresses at least one point from each case.\n\nIf your devil's advocate is less than 3 sentences total, you're not engaging with it — try harder.\n\n## Anti-Inflation Check\n\nCheck for a score history file at `.self-eval-scores.jsonl` in the current working directory.\n\nIf the file exists, read it and check the last 5 scores. If 4+ of the last 5 are the same number, flag it:\n> **Warning: Score clustering detected.** Last 5 scores: [list]. Consider whether you're anchoring to a default.\n\nIf the file doesn't exist, ask yourself: \"Would an outside observer rate this the same way I am?\"\n\n## Score Persistence\n\nAfter presenting your evaluation, append one line to `.self-eval-scores.jsonl` in the current working directory:\n\n```json\n{\"date\":\"YYYY-MM-DD\",\"score\":N,\"ambition\":\"Low|Medium|High\",\"execution\":\"Poor|Adequate|Strong\",\"task\":\"1-sentence summary\"}\n```\n\nThis enables the anti-inflation check to work across sessions. If the file doesn't exist, create it.\n\n## Output Format\n\nPresent your evaluation as:\n\n## Self-Evaluation\n\n**Task:** [1-sentence summary of what was attempted]\n**Ambition:** [Low\u002FMedium\u002FHigh] — [1-sentence justification]\n**Execution:** [Poor\u002FAdequate\u002FStrong] — [1-sentence justification]\n\n**Devil's Advocate:**\n- Lower: [why it might deserve less]\n- Higher: [why it might deserve more]\n- Resolution: [final reasoning]\n\n**Score: [1-5]** — [1-sentence final justification]\n","# Self-Eval: Honest Work Evaluation\n\nultrathink\n\n**Tier:** STANDARD\n**Category:** Engineering \u002F Quality\n**Dependencies:** None (prompt-only, no external tools required)\n\n## Description\n\nSelf-eval is a Claude Code skill that produces honest, calibrated work evaluations. It replaces the default AI tendency to rate everything 4\u002F5 with a structured two-axis scoring system, mandatory devil's advocate reasoning, and cross-session anti-inflation detection.\n\nThe core insight: AI self-assessment converges to \"everything is a 4\" because a single-axis score conflates task difficulty with execution quality. Self-eval separates these axes, then combines them via a fixed matrix that the model cannot override.\n\n## Features\n\n- **Two-axis scoring** — Independently rates task ambition (Low\u002FMedium\u002FHigh) and execution quality (Poor\u002FAdequate\u002FStrong), then combines via a lookup matrix\n- **Mandatory devil's advocate** — Before finalizing, must argue for both higher AND lower scores, then resolve the tension\n- **Score persistence** — Appends scores to `.self-eval-scores.jsonl` in the working directory, building history across sessions\n- **Anti-inflation detection** — Reads past scores and flags clustering (4+ of last 5 identical)\n- **Matrix-locked scoring** — The composite score comes from the matrix, not from direct selection. Low ambition caps at 2\u002F5 regardless of execution quality\n\n## Usage\n\nAfter completing work in a Claude Code session:\n\n```\n\u002Fself-eval\n```\n\nWith context about what to evaluate:\n\n```\n\u002Fself-eval the authentication refactor we just completed\n```\n\nThe skill reviews the conversation history, identifies what was accomplished, scores it on both axes, runs the devil's advocate check, and appends the result to the score history file.\n\n## Examples\n\n### Example 1: Feature Implementation\n\n```\n\u002Fself-eval added pagination to the user list API\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Added cursor-based pagination to the user list API endpoint\n**Ambition:** Medium — New feature with established patterns, but required careful backwards compatibility\n**Execution:** Strong — All tests pass, handles edge cases, existing clients unaffected\n\n**Devil's Advocate:**\n- Lower: Pagination is well-documented. The pattern was copied from another endpoint with minor changes. Could argue Low ambition.\n- Higher: The backwards-compat requirement made this harder than a greenfield implementation. Had to support both offset and cursor modes.\n- Resolution: Medium ambition holds — the backwards-compat constraint added real complexity beyond copy-paste.\n\n**Score: 4** — Solid execution on meaningful work with real constraints.\n```\n\n### Example 2: Bug Fix\n\n```\n\u002Fself-eval\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Fixed race condition in the checkout flow causing duplicate orders\n**Ambition:** Medium — Required debugging across 3 services to find the root cause\n**Execution:** Adequate — Fix works but the test only covers the exact scenario reported, not the general class of race conditions\n\n**Devil's Advocate:**\n- Lower: The fix was a single line (adding a mutex). Once found, it was trivial.\n- Higher: Finding the root cause across 3 services took real investigation. The mutex placement required understanding the full flow.\n- Resolution: Medium ambition is correct for the investigation, but execution drops to Adequate — a more thorough fix would address the pattern, not just the instance.\n\n**Score: 3** — Good debugging work but the fix is narrow.\n```\n\n---\n\n## What to Evaluate\n\n$ARGUMENTS\n\nIf no arguments provided, review the full conversation history to identify what was accomplished this session. Summarize the work in one sentence before scoring.\n\n## How to Score — Two-Axis Model\n\nScore on two independent axes, then combine using the matrix. Do NOT pick a number first and rationalize it — rate each axis separately, then read the matrix.\n\n### Axis 1: Task Ambition (what was attempted)\n\nRate the difficulty and risk of what was worked on. NOT how well it was done.\n\n- **Low (1)** — Safe, familiar, routine. No real risk of failure. Examples: minor config changes, simple refactors, copy-paste with small modifications, tasks you were confident you'd complete before starting.\n- **Medium (2)** — Meaningful work with novelty or challenge. Partial failure was possible. Examples: new feature implementation, integrating an unfamiliar API, architectural changes, debugging a tricky issue.\n- **High (3)** — Ambitious, unfamiliar, or high-stakes. Real risk of complete failure. Examples: building something from scratch in an unfamiliar domain, complex system redesign, performance-critical optimization, shipping to production under pressure.\n\n**Self-check:** If you were confident of success before starting, ambition is Low or Medium, not High.\n\n### Axis 2: Execution Quality (how well it was done)\n\nRate the quality of the actual output, independent of how ambitious the task was.\n\n- **Poor (1)** — Major failures, incomplete, wrong output, or abandoned mid-task. The deliverable doesn't meet its own stated criteria.\n- **Adequate (2)** — Completed but with gaps, shortcuts, or missing rigor. Did the thing but left obvious improvements on the table.\n- **Strong (3)** — Well-executed, thorough, quality output. No obvious improvements left undone given the scope.\n\n### Composite Score Matrix\n\n|                        | Poor Exec (1) | Adequate Exec (2) | Strong Exec (3) |\n|------------------------|:---:|:---:|:---:|\n| **Low Ambition (1)**   |  1  |  2  |  2  |\n| **Medium Ambition (2)**|  2  |  3  |  4  |\n| **High Ambition (3)**  |  2  |  4  |  5  |\n\n**Read the matrix, don't override it.** The composite is your score. The devil's advocate below can cause you to re-rate an axis — but you cannot directly override the matrix result.\n\nKey properties:\n- Low ambition caps at 2. Safe work done perfectly is still safe work.\n- A 5 requires BOTH high ambition AND strong execution. It should be rare.\n- High ambition + poor execution = 2. Bold failure hurts.\n- The most common honest score for solid work is 3 (medium ambition, adequate execution).\n\n## Devil's Advocate (MANDATORY)\n\nBefore writing your final score, you MUST write all three of these:\n\n1. **Case for LOWER:** Why might this work deserve a lower score? What was easy, what was avoided, what was less ambitious than it appears? Would a skeptical reviewer agree with your axis ratings?\n2. **Case for HIGHER:** Why might this work deserve a higher score? What was genuinely challenging, surprising, or exceeded the original plan?\n3. **Resolution:** If either case reveals you mis-rated an axis, re-rate it and recompute the matrix result. Then state your final score with a 1-2 sentence justification that addresses at least one point from each case.\n\nIf your devil's advocate is less than 3 sentences total, you're not engaging with it — try harder.\n\n## Anti-Inflation Check\n\nCheck for a score history file at `.self-eval-scores.jsonl` in the current working directory.\n\nIf the file exists, read it and check the last 5 scores. If 4+ of the last 5 are the same number, flag it:\n> **Warning: Score clustering detected.** Last 5 scores: [list]. Consider whether you're anchoring to a default.\n\nIf the file doesn't exist, ask yourself: \"Would an outside observer rate this the same way I am?\"\n\n## Score Persistence\n\nAfter presenting your evaluation, append one line to `.self-eval-scores.jsonl` in the current working directory:\n\n```json\n{\"date\":\"YYYY-MM-DD\",\"score\":N,\"ambition\":\"Low|Medium|High\",\"execution\":\"Poor|Adequate|Strong\",\"task\":\"1-sentence summary\"}\n```\n\nThis enables the anti-inflation check to work across sessions. If the file doesn't exist, create it.\n\n## Output Format\n\nPresent your evaluation as:\n\n## Self-Evaluation\n\n**Task:** [1-sentence summary of what was attempted]\n**Ambition:** [Low\u002FMedium\u002FHigh] — [1-sentence justification]\n**Execution:** [Poor\u002FAdequate\u002FStrong] — [1-sentence justification]\n\n**Devil's Advocate:**\n- Lower: [why it might deserve less]\n- Higher: [why it might deserve more]\n- Resolution: [final reasoning]\n\n**Score: [1-5]** — [1-sentence final justification]\n",{"name":5,"license":15,"description":7},"main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fself-eval","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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill self-eval",{"tool":64,"command":65},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill self-eval",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill self-eval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fself-eval\u002FSKILL.md",true,[],[73,102,126,153,178,200],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":44},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[83,84,85,86,87,88,89,90,91,92,93,94,29,95,96,97,98,99,100,101],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"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",[],[109,110,111,112,87,113,114,115,116,117,118,119,120,121,34,122,123,124,125,98],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","platform","grow","posting","competitive",{"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":135,"publishedAt":44},"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",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,120,137,138,139,140,141,142,34,143,144,49,145,146,147,148,149,150,151,152],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":44},"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",[],[160,161,162,163,164,165,166,167,168,34,169,94,170,171,172,173,174,175,176,177],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":44},"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",[184],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[186,187,188,189,190,138,165,40,191,192,193,194,120,195,93,30,196,197,198,199],"workflow","workflow builder","builder","design","workflows","orchestrate","pipeline","loop","multi-agent","context","fresh","scripts","judge","claude code workflow",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":44},"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",[],[43,207,208,209,210,211,212,213,214,193,215,216,217,218,219,220,29,221,222,177],"weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]