[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BX0M41NSSHYBGPX0C9RXCS":3,"skill-same:01M7BX0M41NSSHYBGPX0C9RXCS":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7BX0M41NSSHYBGPX0C9RXCS","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.","azhri1990\u002Fproject-genesis","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7BMC0XAE6SV0VTKWP3EMFGZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"description":7,"argument-hint":28},{"version":25,"build_pattern":26,"distinct_from":27},"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","456c0680145b74fe0168cc63541f08eda89e53c0","claude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-09-27 20:56:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fproject-genesis --skill memory-engineering",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill memory-engineering",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill memory-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002FSKILL.md",true,[49,55,59,63,69,73,77,81,87,91,95],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fforgetting_policy_template.md","ASSET","资产文件",4511,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fassets\u002Fforgetting_policy_template.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fmemory_design_spec.example.json",2098,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fassets\u002Fmemory_design_spec.example.json",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fmemory_engineer_worksheet.md",5439,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fassets\u002Fmemory_engineer_worksheet.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fforgetting_policy_design.md","REFERENCE","参考文档",8877,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Freferences\u002Fforgetting_policy_design.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fmemory_control_and_governance.md",7544,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Freferences\u002Fmemory_control_and_governance.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fmemory_cost_canon.md",7030,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Freferences\u002Fmemory_cost_canon.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fwhat_to_keep.md",7786,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Freferences\u002Fwhat_to_keep.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fforgetting_policy_linter.py","SCRIPT","脚本",15509,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fscripts\u002Fforgetting_policy_linter.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fmemory_architecture_picker.py",15780,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fscripts\u002Fmemory_architecture_picker.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fmemory_cost_profiler.py",13675,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fscripts\u002Fmemory_cost_profiler.py",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fmemory_density_auditor.py",26561,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fmemory-engineering\u002Fscripts\u002Fmemory_density_auditor.py",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7C0EZY9FK6JW3YAC7CN17KY","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7C0EA12FWRZTMG0N23HV68M","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"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":120,"publishedAt":19},"01M7C0DXEHJKMKTB4N6B7MS4BT","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7C0DJM5ECEKZXTQA9G6YHQZ","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7C0D304Z7YX7J25R42N6W2T","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7C0CP1419VDF6SGCDY6ZRZV","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]