[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJDPNDCW0VY9CB6W95D2KZ":3,"skill-same:01M6QJDPNDCW0VY9CB6W95D2KZ":85},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6QJDPNDCW0VY9CB6W95D2KZ","memory-engineering",null,"Use when designing, reviewing, or paying for an agent memory system — adding memory to an agent, choosing between long-context \u002F RAG \u002F graph \u002F agentic memory, auditing what a CLAUDE.md or memory directory actually holds, deciding what to keep and what to expire, or when a memory store keeps growing and nobody has said what leaves it. Prices the write path, picks which cost to pay, classifies records as facts \u002F skills \u002F logs, and refuses a design that has no forgetting policy.","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\u002Fmemory-engineering\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"memory","engineering","memory engineering","SkillOpt","design spec","prices","which","pay","sleep","consolidation","lens","agent memory system","memory system","design","agent-harness","question","loop","wiki","logs","agentic","2026-11-10 10:12:30",false,"---\nname: memory-engineering\ndescription: Use when designing, reviewing, or paying for an agent memory system — adding memory to an agent, choosing between long-context \u002F RAG \u002F graph \u002F agentic memory, auditing what a CLAUDE.md or memory directory actually holds, deciding what to keep and what to expire, or when a memory store keeps growing and nobody has said what leaves it. Prices the write path, picks which cost to pay, classifies records as facts \u002F skills \u002F logs, and refuses a design that has no forgetting policy.\nargument-hint: \"[optional: path to a memory dir, design spec JSON, or a question]\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  build_pattern: \"Four-lens synthesis (Stanford \u002F Microsoft \u002F Anthropic \u002F Nvidia) + 4 deterministic stdlib scripts, with a blocking forgetting gate\"\n  distinct_from: \"llm-wiki (maintains one specific markdown vault; this audits and prices any memory system); skillopt-sleep (runs a nightly consolidation loop; this decides whether that loop's output is worth keeping); agent-harness (bounds a task loop; this bounds a store)\"\n---\n\n# Memory Engineering — engineer the forgetting, not just the remembering\n\n> **Portability:** 4 stdlib scripts, no APIs\u002FLLM calls\u002Fnetwork. They measure and gate; you decide.\n\n## What this does\n\nAnyone can give an agent memory: vector store, pipe in the history, retrieve\ntop-k. That works until the history outgrows the context window, the write path\ncosts more than every query it serves, and the store fills with stale state\nnobody removes. Memory is not a bucket — it is a system with a metabolism.\n\n**The shift:** a storer optimizes what a system remembers; a memory engineer\noptimizes what it forgets. The problem was never that an agent forgets — it is\nthat it never forgets *on purpose*.\n\n## The four lenses\n\n| Lens | Question | The finding that hurts |\n|---|---|---|\n| **Stanford** | What does remembering cost? | Construction energy exceeds total query energy across 300 queries. The tuned half is the smaller half. |\n| **Microsoft** | What is worth keeping? | More raw memory can make an agent *worse*. Keep facts and skills; drop the events. |\n| **Anthropic** | Who controls what it keeps? | A wrong memory does not fail once — it persists into every future session that reads it. |\n| **Nvidia** | Where does it hit hardware? | It is all KV cache in HBM. Construction is prefill-heavy and stalls the query a user is waiting on. |\n\n## Workflow\n\n```bash\n# 1 - Price it first. Never quote a quality number without a cost number.\npython scripts\u002Fmemory_cost_profiler.py --print-sample-spec > workload.json\npython scripts\u002Fmemory_cost_profiler.py --spec workload.json\n# 2 - Pick which cost to pay. No \"best\" verdict; on a tie it asks, exit 2.\npython scripts\u002Fmemory_architecture_picker.py --constraints workload.json\n# 3 - Audit what the store actually holds (skip if greenfield).\npython scripts\u002Fmemory_density_auditor.py --dir ~\u002F.claude\u002Fmemory\n# 4 - Gate on forgetting. Exit 4 is a stop, not a suggestion.\npython scripts\u002Fforgetting_policy_linter.py --policy design.json\n# 5 - No command. Prove each pass by hand before scheduling it.\n```\n\nStep 1 reports the construction\u002Fquery split, **cost per correct answer**, and\namortization — if construction dominates, cut construction tokens *before*\ntouching retrieval. Step 2 names the cost the winning family makes you pay.\nStep 3 classifies records FACT \u002F SKILL \u002F LOG \u002F PROSE (`LOG-HEAVY` = archiving\nevents; `PROSE-HEAVY` = docs, not memory).\n\nStep 4 is the gate: **F1** (explicit forgetting rule) and **F4** (contradictions\nsurfaced, never auto-merged) are blocking. Retrofitting forgetting onto two\nyears of records is a migration nobody does; auto-merging disagreeing memories\ndestroys the evidence the conflict existed.\n\nStep 5 has no script — prove each pass by hand, then automate. Run it once\nagainst real history and ask whether it changed a decision. If not, scheduling\nit only makes noise. Ship order: `forgetting_policy_design.md` §7.\n\n## Hard rules\n\n1. **Never quote accuracy without cost per correct answer.**\n2. **Never return a \"best\" memory system** — name the cost the choice makes you pay.\n3. **Never auto-merge contradictions.** The system surfaces; the human decides.\n4. **Never call a design done without a forgetting rule.** No evaluated system provides one by default.\n5. **Never schedule a pass not yet run by hand.**\n6. **Report findings as findings.** A non-zero exit is a result to surface, not an error to swallow.\n7. **Attribute every number** with its confidence level. Vendor customer figures are testimonials, not benchmarks.\n\n## Scripts\n\n| Script | Role | Exit codes |\n|---|---|---|\n| `scripts\u002Fmemory_cost_profiler.py` | Construction vs query split, cost per correct answer, amortization, co-location warning | 0 · 2 finding · 3 bad input |\n| `scripts\u002Fmemory_architecture_picker.py` | Scores 4 families, disqualifies, names the cost, refuses to pick on a tie | 0 · 2 ambiguous · 3 bad input · 4 none viable |\n| `scripts\u002Fmemory_density_auditor.py` | FACT\u002FSKILL\u002FLOG\u002FPROSE, duplicates, staleness, density (`--dir` or `--jsonl`) | 0 dense · 2 finding · 3 bad input |\n| `scripts\u002Fforgetting_policy_linter.py` | The gate: 8 checks, F1 and F4 blocking | 0 PASS · 2 CONDITIONAL · 4 FAIL |\n\nAll support `--output json` and `--sample` (no input file needed).\n\n## References and assets\n\n- [`references\u002Fmemory_cost_canon.md`](references\u002Fmemory_cost_canon.md) — construction dominance, energy per correct answer, the four families, ten recommendations (7 sources)\n- [`references\u002Fwhat_to_keep.md`](references\u002Fwhat_to_keep.md) — PlugMem and MEMENTO: facts over logs, density over volume (7 sources)\n- [`references\u002Fmemory_control_and_governance.md`](references\u002Fmemory_control_and_governance.md) — memory as files, scope\u002Faudit\u002Frollback, poisoning, reading vendor numbers (7 sources)\n- [`references\u002Fforgetting_policy_design.md`](references\u002Fforgetting_policy_design.md) — forgetting mechanisms, contradiction discipline, KV cache, ship order (7 sources)\n- [`assets\u002Fmemory_engineer_worksheet.md`](assets\u002Fmemory_engineer_worksheet.md) — seven forcing questions with recommended answers + citations; walk one at a time\n- [`assets\u002Fmemory_design_spec.example.json`](assets\u002Fmemory_design_spec.example.json) — one file covering every script's input\n- [`assets\u002Fforgetting_policy_template.md`](assets\u002Fforgetting_policy_template.md) — fillable policy covering F1–F8\n\n## Provenance\n\nFraming from *\"How to be a Memory Engineer\"* by [@N01ennn](https:\u002F\u002Fx.com\u002FN01ennn\u002Fstatus\u002F2083971749079581120); every\nnumber is cited to a primary source instead, and two paraphrases are corrected — `memory_cost_canon.md` §2, `memory_control_and_governance.md` §4.\n","# Memory Engineering — engineer the forgetting, not just the remembering\n\n> **Portability:** 4 stdlib scripts, no APIs\u002FLLM calls\u002Fnetwork. They measure and gate; you decide.\n\n## What this does\n\nAnyone can give an agent memory: vector store, pipe in the history, retrieve\ntop-k. That works until the history outgrows the context window, the write path\ncosts more than every query it serves, and the store fills with stale state\nnobody removes. Memory is not a bucket — it is a system with a metabolism.\n\n**The shift:** a storer optimizes what a system remembers; a memory engineer\noptimizes what it forgets. The problem was never that an agent forgets — it is\nthat it never forgets *on purpose*.\n\n## The four lenses\n\n| Lens | Question | The finding that hurts |\n|---|---|---|\n| **Stanford** | What does remembering cost? | Construction energy exceeds total query energy across 300 queries. The tuned half is the smaller half. |\n| **Microsoft** | What is worth keeping? | More raw memory can make an agent *worse*. Keep facts and skills; drop the events. |\n| **Anthropic** | Who controls what it keeps? | A wrong memory does not fail once — it persists into every future session that reads it. |\n| **Nvidia** | Where does it hit hardware? | It is all KV cache in HBM. Construction is prefill-heavy and stalls the query a user is waiting on. |\n\n## Workflow\n\n```bash\n# 1 - Price it first. Never quote a quality number without a cost number.\npython scripts\u002Fmemory_cost_profiler.py --print-sample-spec > workload.json\npython scripts\u002Fmemory_cost_profiler.py --spec workload.json\n# 2 - Pick which cost to pay. No \"best\" verdict; on a tie it asks, exit 2.\npython scripts\u002Fmemory_architecture_picker.py --constraints workload.json\n# 3 - Audit what the store actually holds (skip if greenfield).\npython scripts\u002Fmemory_density_auditor.py --dir ~\u002F.claude\u002Fmemory\n# 4 - Gate on forgetting. Exit 4 is a stop, not a suggestion.\npython scripts\u002Fforgetting_policy_linter.py --policy design.json\n# 5 - No command. Prove each pass by hand before scheduling it.\n```\n\nStep 1 reports the construction\u002Fquery split, **cost per correct answer**, and\namortization — if construction dominates, cut construction tokens *before*\ntouching retrieval. Step 2 names the cost the winning family makes you pay.\nStep 3 classifies records FACT \u002F SKILL \u002F LOG \u002F PROSE (`LOG-HEAVY` = archiving\nevents; `PROSE-HEAVY` = docs, not memory).\n\nStep 4 is the gate: **F1** (explicit forgetting rule) and **F4** (contradictions\nsurfaced, never auto-merged) are blocking. Retrofitting forgetting onto two\nyears of records is a migration nobody does; auto-merging disagreeing memories\ndestroys the evidence the conflict existed.\n\nStep 5 has no script — prove each pass by hand, then automate. Run it once\nagainst real history and ask whether it changed a decision. If not, scheduling\nit only makes noise. Ship order: `forgetting_policy_design.md` §7.\n\n## Hard rules\n\n1. **Never quote accuracy without cost per correct answer.**\n2. **Never return a \"best\" memory system** — name the cost the choice makes you pay.\n3. **Never auto-merge contradictions.** The system surfaces; the human decides.\n4. **Never call a design done without a forgetting rule.** No evaluated system provides one by default.\n5. **Never schedule a pass not yet run by hand.**\n6. **Report findings as findings.** A non-zero exit is a result to surface, not an error to swallow.\n7. **Attribute every number** with its confidence level. Vendor customer figures are testimonials, not benchmarks.\n\n## Scripts\n\n| Script | Role | Exit codes |\n|---|---|---|\n| `scripts\u002Fmemory_cost_profiler.py` | Construction vs query split, cost per correct answer, amortization, co-location warning | 0 · 2 finding · 3 bad input |\n| `scripts\u002Fmemory_architecture_picker.py` | Scores 4 families, disqualifies, names the cost, refuses to pick on a tie | 0 · 2 ambiguous · 3 bad input · 4 none viable |\n| `scripts\u002Fmemory_density_auditor.py` | FACT\u002FSKILL\u002FLOG\u002FPROSE, duplicates, staleness, density (`--dir` or `--jsonl`) | 0 dense · 2 finding · 3 bad input |\n| `scripts\u002Fforgetting_policy_linter.py` | The gate: 8 checks, F1 and F4 blocking | 0 PASS · 2 CONDITIONAL · 4 FAIL |\n\nAll support `--output json` and `--sample` (no input file needed).\n\n## References and assets\n\n- [`references\u002Fmemory_cost_canon.md`](references\u002Fmemory_cost_canon.md) — construction dominance, energy per correct answer, the four families, ten recommendations (7 sources)\n- [`references\u002Fwhat_to_keep.md`](references\u002Fwhat_to_keep.md) — PlugMem and MEMENTO: facts over logs, density over volume (7 sources)\n- [`references\u002Fmemory_control_and_governance.md`](references\u002Fmemory_control_and_governance.md) — memory as files, scope\u002Faudit\u002Frollback, poisoning, reading vendor numbers (7 sources)\n- [`references\u002Fforgetting_policy_design.md`](references\u002Fforgetting_policy_design.md) — forgetting mechanisms, contradiction discipline, KV cache, ship order (7 sources)\n- [`assets\u002Fmemory_engineer_worksheet.md`](assets\u002Fmemory_engineer_worksheet.md) — seven forcing questions with recommended answers + citations; walk one at a time\n- [`assets\u002Fmemory_design_spec.example.json`](assets\u002Fmemory_design_spec.example.json) — one file covering every script's input\n- [`assets\u002Fforgetting_policy_template.md`](assets\u002Fforgetting_policy_template.md) — fillable policy covering F1–F8\n\n## Provenance\n\nFraming from *\"How to be a Memory Engineer\"* by [@N01ennn](https:\u002F\u002Fx.com\u002FN01ennn\u002Fstatus\u002F2083971749079581120); every\nnumber is cited to a primary source instead, and two paraphrases are corrected — `memory_cost_canon.md` §2, `memory_control_and_governance.md` §4.\n",{"name":5,"license":15,"metadata":57,"description":7,"argument-hint":61},{"version":58,"build_pattern":59,"distinct_from":60},"1.0.0","Four-lens synthesis (Stanford \u002F Microsoft \u002F Anthropic \u002F Nvidia) + 4 deterministic stdlib scripts, with a blocking forgetting gate","llm-wiki (maintains one specific markdown vault; this audits and prices any memory system); skillopt-sleep (runs a nightly consolidation loop; this decides whether that loop's output is worth keeping); agent-harness (bounds a task loop; this bounds a store)","[optional: path to a memory dir, design spec JSON, or a question]","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fmemory-engineering","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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill memory-engineering",{"tool":77,"command":78},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill memory-engineering",{"tool":80,"command":81},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill memory-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmemory-engineering\u002FSKILL.md",true,[],[86,116,140,165,190,212],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":52},"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",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":52},"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",[],[123,124,125,126,100,127,33,128,129,130,131,132,133,134,135,136,137,138,139,112],"twitter","x twitter growth","growth","research","content","plan","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":52},"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",[146],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[148,133,149,150,151,152,153,154,135,155,156,62,157,158,159,160,161,162,163,164],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":52},"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",[],[172,173,174,175,176,177,178,179,180,135,181,107,182,183,184,185,186,187,188,189],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":52},"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",[196],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[198,199,200,45,201,150,177,202,203,204,48,205,133,206,106,207,208,209,210,211],"workflow","workflow builder","builder","workflows","code","orchestrate","pipeline","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":52},"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",[],[219,220,221,222,223,224,225,226,227,48,228,229,230,231,232,233,108,234,235,189],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]