[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PVDE4XZ05FP4AWY3Y565N0":3,"skill-same:01M6PVDE4XZ05FP4AWY3Y565N0":63},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":42,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6PVDE4XZ05FP4AWY3Y565N0","task-summary",null,"Focused post-task summary covering architectural decisions, decision forks, pitfalls, and plan deviations. Use at `document → review`, before handing the card to the reviewer, on a task that failed, or when the supervisor asks what happened with a task.","muratovv\u002Fai-hats","muratovv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7502801?v=4","01M6JGCBN4KEJX012GPJVSH04T","Fedor Muratov","01M6JGCBSNMN7CW3RGTPPE0MN2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fcore\u002Fskills\u002Ftask-summary\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"task","summary","task summary","review","plan","supervisor","decision","reviewer","decisions","use","document","card","post","with","pitfalls","at","2026-11-10 10:12:30",false,"---\nname: task-summary\ndescription: >-\n  Focused post-task summary covering architectural decisions, decision\n  forks, pitfalls, and plan deviations. Use at `document → review`, before\n  handing the card to the reviewer, on a task that failed, or when the\n  supervisor asks what happened with a task.\nlicense: MIT\nai_hats:\n  schema_version: 1\n  type: skill\n---\n\n# Task Summary\n\nProduce a focused summary of a completed task, capturing only decision-critical knowledge.\n\n## When to Use\n\nThe backward-looking *factual record* of a finished task — what was decided and\nwhy. It is due at `document → review`: `summary.md` is what the reviewer opens,\nso it is attached before the card enters `review`, not after it leaves (see\n**hatrack**'s per-edge table). Two siblings to keep distinct:\n\n- **self-retrospective** is the *improvement* analysis (5-whys, systemic fixes)\n  of how the work went — run that when there were failures or backtracks; this\n  skill just records the outcome.\n- **context-handoff** is the *forward* brief for whoever continues the work —\n  task-summary looks back, handoff looks ahead.\n\n## Procedure\n\n1. **Identify the task:** Locate the task card in `\u003Cai_hats_dir>\u002Ftracker\u002Fbacklog\u002Ftasks\u002F\u003CID>\u002F`.\n\n2. **Extract decision-critical information:**\n   - **Architectural decisions** — what structural choices were made and WHY\n   - **Decision forks** — where were there multiple viable options?\n     Document: what options existed, which was chosen, and the key reason\n   - **Pitfalls discovered** — non-obvious traps that cost time or could bite again\n   - **Deviations from plan** — where did execution diverge from the original plan and why\n\n3. **Draft the summary** at a scratch path outside the backlog — e.g.\n   `\u002Ftmp\u002F\u003CID>-summary.md`. Do not write it under `tasks\u002F\u003CID>\u002F` yourself;\n   step 4 puts it there:\n\n```markdown\n# Summary: \u003Ctask title>\n\nCompleted: YYYY-MM-DD\nResult: \u003Cdone | failed>\n\n## What Was Done\n\n\u003C2-5 sentences. Outcome, not play-by-play.>\n\n## Key Decisions\n\n| Decision | Why This Way | Alternative Rejected |\n| -------- | ------------ | -------------------- |\n| ...      | ...          | ...                  |\n\n## Pitfalls\n\n- \u003CNon-obvious trap> — \u003Cimpact or how to avoid>\n\n## Deviations from Plan\n\n- \u003CWhat changed> — \u003Cwhy>\n```\n\n4. **Attach it to the card:**\n\n   ```bash\n   rack transition \u003CID> --attach \u002Ftmp\u002F\u003CID>-summary.md:summary.md\n   ```\n\n   The file is copied to `tasks\u002F\u003CID>\u002Fsummary.md` — a document, discovered live by\n   `rack context` (name + digest computed on the fly, fs-as-truth). `--attach` is\n   the sanctioned way in: the backlog gate refuses a hand edit under\n   `tasks\u002F\u003CID>\u002F**`, carving out `plan.md` alone. Re-attaching the same\n   name overwrites (the op notes it); `--freeze summary.md` pins its digest.\n\n## What NOT to Include\n\n- Step-by-step log of actions (that's `work_log` in the task card)\n- Routine operations (git commits, file reads, linting)\n- Information already in the code or commit messages\n- Full error traces (reference file paths instead)\n\n## Completion\n\n- Summary drafted outside the backlog tree, then attached via `rack transition --attach`\n- Contains at least: What Was Done, Key Decisions\n- `rack context \u003CID>` lists `summary.md` under its documents\n\n## Anti-Patterns\n\n- Summarizing everything — the point is filtering, not transcription\n- Missing the WHY — a list of facts without reasoning helps nobody\n- Writing the summary without reading the task's work_log first — you'll miss context\n- Writing the summary under `tasks\u002F\u003CID>\u002F` by hand — `summary.md` there, or a\n  `summary_file:` key in task.yaml. Both break the backlog gate, and no\n  CLI writes either. `rack transition \u003CID> --attach` is the door\n","# Task Summary\n\nProduce a focused summary of a completed task, capturing only decision-critical knowledge.\n\n## When to Use\n\nThe backward-looking *factual record* of a finished task — what was decided and\nwhy. It is due at `document → review`: `summary.md` is what the reviewer opens,\nso it is attached before the card enters `review`, not after it leaves (see\n**hatrack**'s per-edge table). Two siblings to keep distinct:\n\n- **self-retrospective** is the *improvement* analysis (5-whys, systemic fixes)\n  of how the work went — run that when there were failures or backtracks; this\n  skill just records the outcome.\n- **context-handoff** is the *forward* brief for whoever continues the work —\n  task-summary looks back, handoff looks ahead.\n\n## Procedure\n\n1. **Identify the task:** Locate the task card in `\u003Cai_hats_dir>\u002Ftracker\u002Fbacklog\u002Ftasks\u002F\u003CID>\u002F`.\n\n2. **Extract decision-critical information:**\n   - **Architectural decisions** — what structural choices were made and WHY\n   - **Decision forks** — where were there multiple viable options?\n     Document: what options existed, which was chosen, and the key reason\n   - **Pitfalls discovered** — non-obvious traps that cost time or could bite again\n   - **Deviations from plan** — where did execution diverge from the original plan and why\n\n3. **Draft the summary** at a scratch path outside the backlog — e.g.\n   `\u002Ftmp\u002F\u003CID>-summary.md`. Do not write it under `tasks\u002F\u003CID>\u002F` yourself;\n   step 4 puts it there:\n\n```markdown\n# Summary: \u003Ctask title>\n\nCompleted: YYYY-MM-DD\nResult: \u003Cdone | failed>\n\n## What Was Done\n\n\u003C2-5 sentences. Outcome, not play-by-play.>\n\n## Key Decisions\n\n| Decision | Why This Way | Alternative Rejected |\n| -------- | ------------ | -------------------- |\n| ...      | ...          | ...                  |\n\n## Pitfalls\n\n- \u003CNon-obvious trap> — \u003Cimpact or how to avoid>\n\n## Deviations from Plan\n\n- \u003CWhat changed> — \u003Cwhy>\n```\n\n4. **Attach it to the card:**\n\n   ```bash\n   rack transition \u003CID> --attach \u002Ftmp\u002F\u003CID>-summary.md:summary.md\n   ```\n\n   The file is copied to `tasks\u002F\u003CID>\u002Fsummary.md` — a document, discovered live by\n   `rack context` (name + digest computed on the fly, fs-as-truth). `--attach` is\n   the sanctioned way in: the backlog gate refuses a hand edit under\n   `tasks\u002F\u003CID>\u002F**`, carving out `plan.md` alone. Re-attaching the same\n   name overwrites (the op notes it); `--freeze summary.md` pins its digest.\n\n## What NOT to Include\n\n- Step-by-step log of actions (that's `work_log` in the task card)\n- Routine operations (git commits, file reads, linting)\n- Information already in the code or commit messages\n- Full error traces (reference file paths instead)\n\n## Completion\n\n- Summary drafted outside the backlog tree, then attached via `rack transition --attach`\n- Contains at least: What Was Done, Key Decisions\n- `rack context \u003CID>` lists `summary.md` under its documents\n\n## Anti-Patterns\n\n- Summarizing everything — the point is filtering, not transcription\n- Missing the WHY — a list of facts without reasoning helps nobody\n- Writing the summary without reading the task's work_log first — you'll miss context\n- Writing the summary under `tasks\u002F\u003CID>\u002F` by hand — `summary.md` there, or a\n  `summary_file:` key in task.yaml. Both break the backlog gate, and no\n  CLI writes either. `rack transition \u003CID> --attach` is the door\n",{"name":5,"ai_hats":40,"license":15,"description":7},{"type":41,"schema_version":42},"skill",1,"master","f922a7f627276366873d546942d9ad899a86f71a","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fcore\u002Fskills\u002Ftask-summary","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add muratovv\u002Fai-hats --skill task-summary",{"tool":55,"command":56},"bunx","bunx skills add muratovv\u002Fai-hats --skill task-summary",{"tool":58,"command":59},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill task-summary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fcore\u002Fskills\u002Ftask-summary\u002FSKILL.md",true,[],[64,90,114,137,161,175],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":35},"01M6PVFB1SM738R2SRSRSF7CY6","tool-evaluation-protocol","Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML\u002FLLM frameworks, testing approaches), or following up on a hype-driven recommendation.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Ftool-evaluation-protocol\u002FSKILL.md",[],[71,72,73,74,75,76,77,78,79,80,28,81,82,83,84,85,86,87,88,89],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","dependency","up","frameworks","time","project","recommendation","for","bounded","candidate",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":35},"01M6PVF7HATBEX1G7N50E2QT57","systematic-debugging","4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[97,98,99,100,71,101,102,103,104,105,28,106,107,108,109,110,111,32,112,113],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","bug-fix","phase",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":35},"01M6PVF3MTQN3RPF73AN34856J","skill-template","Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-template\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[126,127,128,129,130,104,131,28,132,109,133,134,135,87,136],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":35},"01M6PVF06SCV28QARM5MQPANC9","skill-optimization","Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-optimization\u002FSKILL.md",[143],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[145,146,147,148,149,150,151,152,153,154,28,155,156,157,158,159,160],"Optimization","skill optimization","components","component","issues","library","audit","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":35},"01M6PVEXM9717016T9MW82HDCT","silent-fallback-gate","PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsilent-fallback-gate\u002FSKILL.md",[],[168,169,170,171,172,173,28,174,87],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":35},"01M6PVESM49C5NT7SB7N3F76VS","retro-to-framework","Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fretro-to-framework\u002FSKILL.md",[181],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[183,184,185,186,148,187,188,189,154,104,28,190,191,85,192,193,194,195,196,197],"framework","retro","retro to framework","change","retrospective","projects","convert","incident","across","problem","about","more","skill update","single","generic"]