[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQGPDDATDMXMGEXC9GS7WS":3,"skill-same:01M7BQGPDDATDMXMGEXC9GS7WS":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BQGPDDATDMXMGEXC9GS7WS","memory-review",null,"Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs \u002Fsi:memory-review or asks what has been learned and what should be promoted or pruned.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fmemory-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"memory-review\"\ndescription: \"Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs \u002Fsi:memory-review or asks what has been learned and what should be promoted or pruned.\"\n---\n\n# \u002Fsi:memory-review — Analyze Auto-Memory\n\nPerforms a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.\n\n## Usage\n\n```\n\u002Fsi:memory-review                    # Full review\n\u002Fsi:memory-review --quick            # Summary only (counts + top 3 candidates)\n\u002Fsi:memory-review --stale            # Focus on stale\u002Foutdated entries\n\u002Fsi:memory-review --candidates       # Show only promotion candidates\n```\n\n## What It Does\n\n### Step 1: Locate memory directory\n\n```bash\n# Find the project's auto-memory directory\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\n\n# Fallback: check common path patterns\n# ~\u002F.claude\u002Fprojects\u002F\u003Cuser>\u002F\u003Cproject>\u002Fmemory\u002F\n# ~\u002F.claude\u002Fprojects\u002F\u003Cabsolute-path>\u002Fmemory\u002F\n\n# List all memory files\nls -la \"$MEMORY_DIR\"\u002F\n```\n\nIf memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with `\u002Fmemory`.\n\n### Step 2: Read and analyze MEMORY.md\n\nRead the full `MEMORY.md` file. Count lines and check against the 200-line startup limit.\n\nAnalyze each entry for:\n\n1. **Recurrence indicators**\n   - Same concept appears multiple times (different wording)\n   - References to \"again\" or \"still\" or \"keeps happening\"\n   - Similar entries across topic files\n\n2. **Staleness indicators**\n   - References files that no longer exist (`find` to verify)\n   - Mentions outdated tools, versions, or commands\n   - Contradicts current CLAUDE.md rules\n\n3. **Consolidation opportunities**\n   - Multiple entries about the same topic (e.g., three lines about testing)\n   - Entries that could merge into one concise rule\n\n4. **Promotion candidates** — entries that meet ALL criteria:\n   - Appeared in 2+ sessions (check wording patterns)\n   - Not project-specific trivia (broadly useful)\n   - Actionable (can be written as a concrete rule)\n   - Not already in CLAUDE.md or `.claude\u002Frules\u002F`\n\n### Step 3: Read topic files\n\nIf `MEMORY.md` references or the directory contains additional files (`debugging.md`, `patterns.md`, etc.):\n- Read each one\n- Cross-reference with MEMORY.md for duplicates\n- Check for entries that belong in the main file (high value) vs. topic files (details)\n\n### Step 4: Cross-reference with CLAUDE.md\n\nRead the project's `CLAUDE.md` (if it exists) and compare:\n- Are there MEMORY.md entries that duplicate CLAUDE.md rules? (→ remove from memory)\n- Are there MEMORY.md entries that contradict CLAUDE.md? (→ flag conflict)\n- Are there MEMORY.md patterns not yet in CLAUDE.md that should be? (→ promotion candidate)\n\nAlso check `.claude\u002Frules\u002F` directory for existing scoped rules.\n\n### Step 5: Generate report\n\nOutput format:\n\n```\n📊 Auto-Memory Review\n\nMemory Health:\n  MEMORY.md:        {{lines}}\u002F200 lines ({{percent}}%)\n  Topic files:      {{count}} ({{names}})\n  CLAUDE.md:        {{lines}} lines\n  Rules:            {{count}} files in .claude\u002Frules\u002F\n\n🎯 Promotion Candidates ({{count}}):\n  1. \"{{pattern}}\" — seen {{n}}x, applies broadly\n     → Suggest: {{target}} (CLAUDE.md \u002F .claude\u002Frules\u002F{{name}}.md)\n  2. ...\n\n🗑️ Stale Entries ({{count}}):\n  1. Line {{n}}: \"{{entry}}\" — {{reason}}\n  2. ...\n\n🔄 Consolidation ({{count}} groups):\n  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry\n  2. ...\n\n⚠️ Conflicts ({{count}}):\n  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}\n\n💡 Recommendations:\n  - {{actionable suggestion}}\n  - {{actionable suggestion}}\n```\n\n## When to Use\n\n- After completing a major feature or debugging session\n- When `\u002Fsi:memory-status` shows MEMORY.md is over 150 lines\n- Weekly during active development\n- Before starting a new project phase\n- After onboarding a new team member (review what Claude learned)\n\n## Tips\n\n- Run `\u002Fsi:memory-review --quick` frequently (low overhead)\n- Full review is most valuable when MEMORY.md is getting crowded\n- Act on promotion candidates promptly — they're proven patterns\n- Don't hesitate to delete stale entries — auto-memory will re-learn if needed\n","# \u002Fsi:memory-review — Analyze Auto-Memory\n\nPerforms a comprehensive audit of Claude Code's auto-memory and produces actionable recommendations.\n\n## Usage\n\n```\n\u002Fsi:memory-review                    # Full review\n\u002Fsi:memory-review --quick            # Summary only (counts + top 3 candidates)\n\u002Fsi:memory-review --stale            # Focus on stale\u002Foutdated entries\n\u002Fsi:memory-review --candidates       # Show only promotion candidates\n```\n\n## What It Does\n\n### Step 1: Locate memory directory\n\n```bash\n# Find the project's auto-memory directory\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\n\n# Fallback: check common path patterns\n# ~\u002F.claude\u002Fprojects\u002F\u003Cuser>\u002F\u003Cproject>\u002Fmemory\u002F\n# ~\u002F.claude\u002Fprojects\u002F\u003Cabsolute-path>\u002Fmemory\u002F\n\n# List all memory files\nls -la \"$MEMORY_DIR\"\u002F\n```\n\nIf memory directory doesn't exist, report that auto-memory may be disabled. Suggest checking with `\u002Fmemory`.\n\n### Step 2: Read and analyze MEMORY.md\n\nRead the full `MEMORY.md` file. Count lines and check against the 200-line startup limit.\n\nAnalyze each entry for:\n\n1. **Recurrence indicators**\n   - Same concept appears multiple times (different wording)\n   - References to \"again\" or \"still\" or \"keeps happening\"\n   - Similar entries across topic files\n\n2. **Staleness indicators**\n   - References files that no longer exist (`find` to verify)\n   - Mentions outdated tools, versions, or commands\n   - Contradicts current CLAUDE.md rules\n\n3. **Consolidation opportunities**\n   - Multiple entries about the same topic (e.g., three lines about testing)\n   - Entries that could merge into one concise rule\n\n4. **Promotion candidates** — entries that meet ALL criteria:\n   - Appeared in 2+ sessions (check wording patterns)\n   - Not project-specific trivia (broadly useful)\n   - Actionable (can be written as a concrete rule)\n   - Not already in CLAUDE.md or `.claude\u002Frules\u002F`\n\n### Step 3: Read topic files\n\nIf `MEMORY.md` references or the directory contains additional files (`debugging.md`, `patterns.md`, etc.):\n- Read each one\n- Cross-reference with MEMORY.md for duplicates\n- Check for entries that belong in the main file (high value) vs. topic files (details)\n\n### Step 4: Cross-reference with CLAUDE.md\n\nRead the project's `CLAUDE.md` (if it exists) and compare:\n- Are there MEMORY.md entries that duplicate CLAUDE.md rules? (→ remove from memory)\n- Are there MEMORY.md entries that contradict CLAUDE.md? (→ flag conflict)\n- Are there MEMORY.md patterns not yet in CLAUDE.md that should be? (→ promotion candidate)\n\nAlso check `.claude\u002Frules\u002F` directory for existing scoped rules.\n\n### Step 5: Generate report\n\nOutput format:\n\n```\n📊 Auto-Memory Review\n\nMemory Health:\n  MEMORY.md:        {{lines}}\u002F200 lines ({{percent}}%)\n  Topic files:      {{count}} ({{names}})\n  CLAUDE.md:        {{lines}} lines\n  Rules:            {{count}} files in .claude\u002Frules\u002F\n\n🎯 Promotion Candidates ({{count}}):\n  1. \"{{pattern}}\" — seen {{n}}x, applies broadly\n     → Suggest: {{target}} (CLAUDE.md \u002F .claude\u002Frules\u002F{{name}}.md)\n  2. ...\n\n🗑️ Stale Entries ({{count}}):\n  1. Line {{n}}: \"{{entry}}\" — {{reason}}\n  2. ...\n\n🔄 Consolidation ({{count}} groups):\n  1. Lines {{a}}, {{b}}, {{c}} all about {{topic}} → merge into 1 entry\n  2. ...\n\n⚠️ Conflicts ({{count}}):\n  1. MEMORY.md line {{n}} contradicts CLAUDE.md: {{detail}}\n\n💡 Recommendations:\n  - {{actionable suggestion}}\n  - {{actionable suggestion}}\n```\n\n## When to Use\n\n- After completing a major feature or debugging session\n- When `\u002Fsi:memory-status` shows MEMORY.md is over 150 lines\n- Weekly during active development\n- Before starting a new project phase\n- After onboarding a new team member (review what Claude learned)\n\n## Tips\n\n- Run `\u002Fsi:memory-review --quick` frequently (low overhead)\n- Full review is most valuable when MEMORY.md is getting crowded\n- Act on promotion candidates promptly — they're proven patterns\n- Don't hesitate to delete stale entries — auto-memory will re-learn if needed\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","engineering-team\u002Fself-improving-agent\u002Fskills\u002Fmemory-review",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill memory-review",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill memory-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill memory-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fmemory-review\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research, deepread for evidence-first reading of supplied documents) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]