[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETHBF6QJBKQAF99BASPVW1":3,"skill-same:01M7ETHBF6QJBKQAF99BASPVW1":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7ETHBF6QJBKQAF99BASPVW1","ams-memory-search",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-memory-search\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: memory-search\ndescription: Search agent memory effectively: recall prior decisions, facts, and context across conversations. Use when an agent needs to remember what was learned before.\ncategory: ai-maestro\n---\n\n# Memory Search\n\n## Overview\n\nAgents without memory start every conversation from zero. Memory systems store durable facts, decisions, preferences, and history — searchable when needed.\n\nEffective memory search: store well (atomic claims, sourced, dated), retrieve with multiple query phrasings, and verify before acting on old memories.\n\nThe pattern: write memories as you learn, search before deciding, and update when facts change.\n\n## When to use\n\n- Agent needs prior context about the user or project\n- Recalling past decisions and their reasoning\n- Finding what was learned in earlier sessions\n- Verifying a fact before acting on it\n- Maintaining continuity across long-running work\n\n## Core concepts\n\n- **Atomic claims.**\n  Store one fact per memory entry: who said it, when, the exact claim. Atomic entries retrieve precisely; paragraphs retrieve vaguely.\n- **Source and date.**\n  Every memory notes its origin (conversation date, document) and timestamp. Old memories need age-checking before use.\n- **Multiple query phrasings.**\n  Search with 2-3 different wordings of the same question. Retrieval is fuzzy — varied phrasings catch what one misses.\n- **Verify before acting.**\n  Retrieved memories are leads, not gospel. Check the source context for anything consequential before acting on it.\n- **Update, don't just add.**\n  When facts change, update or supersede the old memory. Contradictory memories without resolution poison future retrieval.\n- **Salience and decay.**\n  Not all memories matter equally. Boost frequently-used, correct memories; let stale, unused ones fade. Memory needs gardening.\n- **Scoped retrieval.**\n  Search the right store: user preferences vs. project facts vs. session history. Scoped search beats global noise.\n- **Provenance chains.**\n  For important claims, keep the chain: memory -> source conversation -> original evidence. Auditability matters for trust.\n\n## Practical workflow\n\n1. **Capture as you learn.**\n   Durable facts, decisions, preferences -> memory immediately, in atomic form with source and date. Don't batch 'later.'\n2. **Search before deciding.**\n   Before acting on prior work, preferences, or history: search memory with 2-3 phrasings. Make it a habit, not an afterthought.\n3. **Read the context.**\n   For top hits, pull the surrounding source context. A claim without context is easy to misapply.\n4. **Act on verified memories.**\n   Use verified memories to inform decisions; note the memory as the basis so the reasoning is traceable.\n5. **Update on change.**\n   New information contradicting a memory? Update the entry (or mark superseded) immediately. Stale memories are worse than none.\n6. **Garden periodically.**\n   Review memories: still true? Still relevant? Merge duplicates, retire the dead. Monthly for active stores.\n7. **Handle conflicts.**\n   Two memories disagree: check sources and dates, prefer newer + better-sourced, record the resolution.\n8. **Respect privacy.**\n   Memories contain personal data. Scope access, never leak across users, and honor deletion requests completely.\n\n## Common pitfalls\n\n- **Never searching.**\n  Having memory but deciding from scratch each time. The search habit is the whole value proposition.\n- **Single phrasing.**\n  One query, no hits, giving up. Retrieval needs 2-3 varied phrasings — different words catch different entries.\n- **Acting on stale memories.**\n  Using a year-old preference as current fact. Check dates; verify anything consequential.\n- **Memory hoarding.**\n  Storing everything verbatim. Uncurated memory becomes unsearchable noise — atomic, salient, gardened.\n- **Contradictions unresolved.**\n  Old and new memories disagreeing silently. Resolve explicitly or retrieval becomes a coin flip.\n- **No provenance.**\n  Facts without sources. When challenged ('where did you learn that?'), sourceless memories collapse.\n- **Cross-user leakage.**\n  One user's memories surfacing for another. Scope strictly; this is a privacy failure, not a feature.\n- **Treating memory as truth.**\n  Memory is a lead, not evidence. Verify against sources for anything that matters.\n","# Memory Search\n\n## Overview\n\nAgents without memory start every conversation from zero. Memory systems store durable facts, decisions, preferences, and history — searchable when needed.\n\nEffective memory search: store well (atomic claims, sourced, dated), retrieve with multiple query phrasings, and verify before acting on old memories.\n\nThe pattern: write memories as you learn, search before deciding, and update when facts change.\n\n## When to use\n\n- Agent needs prior context about the user or project\n- Recalling past decisions and their reasoning\n- Finding what was learned in earlier sessions\n- Verifying a fact before acting on it\n- Maintaining continuity across long-running work\n\n## Core concepts\n\n- **Atomic claims.**\n  Store one fact per memory entry: who said it, when, the exact claim. Atomic entries retrieve precisely; paragraphs retrieve vaguely.\n- **Source and date.**\n  Every memory notes its origin (conversation date, document) and timestamp. Old memories need age-checking before use.\n- **Multiple query phrasings.**\n  Search with 2-3 different wordings of the same question. Retrieval is fuzzy — varied phrasings catch what one misses.\n- **Verify before acting.**\n  Retrieved memories are leads, not gospel. Check the source context for anything consequential before acting on it.\n- **Update, don't just add.**\n  When facts change, update or supersede the old memory. Contradictory memories without resolution poison future retrieval.\n- **Salience and decay.**\n  Not all memories matter equally. Boost frequently-used, correct memories; let stale, unused ones fade. Memory needs gardening.\n- **Scoped retrieval.**\n  Search the right store: user preferences vs. project facts vs. session history. Scoped search beats global noise.\n- **Provenance chains.**\n  For important claims, keep the chain: memory -> source conversation -> original evidence. Auditability matters for trust.\n\n## Practical workflow\n\n1. **Capture as you learn.**\n   Durable facts, decisions, preferences -> memory immediately, in atomic form with source and date. Don't batch 'later.'\n2. **Search before deciding.**\n   Before acting on prior work, preferences, or history: search memory with 2-3 phrasings. Make it a habit, not an afterthought.\n3. **Read the context.**\n   For top hits, pull the surrounding source context. A claim without context is easy to misapply.\n4. **Act on verified memories.**\n   Use verified memories to inform decisions; note the memory as the basis so the reasoning is traceable.\n5. **Update on change.**\n   New information contradicting a memory? Update the entry (or mark superseded) immediately. Stale memories are worse than none.\n6. **Garden periodically.**\n   Review memories: still true? Still relevant? Merge duplicates, retire the dead. Monthly for active stores.\n7. **Handle conflicts.**\n   Two memories disagree: check sources and dates, prefer newer + better-sourced, record the resolution.\n8. **Respect privacy.**\n   Memories contain personal data. Scope access, never leak across users, and honor deletion requests completely.\n\n## Common pitfalls\n\n- **Never searching.**\n  Having memory but deciding from scratch each time. The search habit is the whole value proposition.\n- **Single phrasing.**\n  One query, no hits, giving up. Retrieval needs 2-3 varied phrasings — different words catch different entries.\n- **Acting on stale memories.**\n  Using a year-old preference as current fact. Check dates; verify anything consequential.\n- **Memory hoarding.**\n  Storing everything verbatim. Uncurated memory becomes unsearchable noise — atomic, salient, gardened.\n- **Contradictions unresolved.**\n  Old and new memories disagreeing silently. Resolve explicitly or retrieval becomes a coin flip.\n- **No provenance.**\n  Facts without sources. When challenged ('where did you learn that?'), sourceless memories collapse.\n- **Cross-user leakage.**\n  One user's memories surfacing for another. Scope strictly; this is a privacy failure, not a feature.\n- **Treating memory as truth.**\n  Memory is a lead, not evidence. Verify against sources for anything that matters.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-memory-search",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-memory-search",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-memory-search",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-memory-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-memory-search\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]