mem-search
Skill2 starsChanged 18 days agoMITView on GitHub
Busca en el historial de sesiones anteriores de Claude Code (lo que dijo el usuario y lo que respondió Claude) sin gastar tokens hasta que se usa. Úsala cuando el usuario pregunte por algo de una sesión pasada ("¿qué decidimos de X?", "¿cómo arreglamos Y la otra vez?", "ya habíamos hablado de esto") y la memoria automática (MEMORY.md) no lo tenga.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- barrelc/kimi-mnemetheir own version, first seen Nov 1, 2026
- susantedit/claude-skillstheir own version, first seen Oct 20, 2026
- oivanfelipe/claude-skillstheir own version, first seen Oct 13, 2026
- satishbabariya/claude-mem-gotheir own version, first seen Oct 1, 2026
- gcapodeferro02/my-agent-skillstheir own version, first seen Sep 21, 2026
Used with
Projects with it also use oh-my-issues, what-the and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
tuliosalustiano27Skilloh-my-issues
Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.
Also in 3 projects that use this
tuliosalustiano27Skillwhat-the
What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.
Also in 3 projects that use this
thedotmackSkillpathfinder
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Also in 4 projects that use this
TrecekSkillmake-plan
Create implementation plans through deep codebase understanding. Use when user asks to create, devise, or write a plan. Leverages subagents to explore approaches, understand systems, and design aligned solutions.
Also in 5 projects that use this
dqtx760Skilltimeline-report
Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
Also in 3 projects that use this
tunnckoCoreSkillhow-it-works
Use for 'how does X work', code walkthroughs before changing something, and placement / ownership / layering questions ('where should this live', 'which package owns this', 'is this the right layer'). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- jorgeasaurus/agent-skills★ 14same name
- barrelc/kimi-mneme★ 9same name
- tleub-ebp/WorkPilot-AI★ 4same name
- dqtx760/skills-manage★ 2same name
- gcapodeferro02/my-agent-skills★ 1same name
- MMACABRE/SKILLS★ 1same name
- pengt1993/claude-skills★ 1same name
- satishbabariya/claude-mem-go★ 1same name
- tuliosalustiano27/Skills_Claude_Code★ 1same name
- HermeticOrmus/mem-search-skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- private-template/CLAUDE.mdCLAUDE.md
- backend-quality-gateSkill
- blindarSkill
- brechasSkill
- crear-appSkill
- desarrollo-por-etapasSkill
- docker-docsSkill
- elegir-metodoSkill
- erp-saas-coreSkill
- fullstackSkill
- graphifySkill
- http-query-docsSkill
- mapa-bloqueSkill
- memory-bank-contextSkill
- microserviciosSkill
- minio-docsSkill
- nestjs-docsSkill
- nestjs-security-hardeningSkill
- nextjs-docsSkill
- prisma7-docsSkill
- prompt-masterSkill
- react-docsSkill
- redis-docsSkill
- skills-bundleSkill
- tailwind-docsSkill
- tanstack-query-docsSkill
- testing-actionsSkill
- typescript-docsSkill
- ui-ux-polishSkill
- zustand-docsSkill
The file
Files
mem-search
Busca en ~/.claude/projects/*/*.jsonl, que es donde Claude Code guarda cada sesión.
Solo lee los mensajes del usuario y el texto de Claude. Deja fuera los resultados de
tools, el thinking y los subagents, así no aparecen datos sensibles ni ruido.
Cuándo
- Primero revisa la memoria automática del proyecto, que ya está en tu contexto (
MEMORY.md). - Si ahí no está, usa este script antes de decir "no sé" o de preguntarle de nuevo al usuario.
Cómo
~/.claude/skills/mem-search/scripts/mem-search.sh [-p proyecto] [-d días] [-n máx] [-c chars] "<regex>"-p erp: solo proyectos cuya carpeta contenga "erp". Úsalo casi siempre con el nombre del repo actual.-d 30: solo sesiones de los últimos 30 días.-n 10: cuántos resultados mostrar. Salen los más recientes primero (default 20).-c 300: más contexto alrededor del match (default 160).
El patrón es una regex que no distingue mayúsculas. Si no te sale nada, prueba con sinónimos y
variantes en el mismo patrón: "multi.?tenant|tenantId|aislamiento".
Cada resultado trae la fecha, la carpeta del proyecto, quién habló (tú o claude), el id de
la sesión y un recorte del texto. Para ver la conversación completa, el usuario puede correr
claude --resume <sesión> desde esa carpeta.
Reglas
- Resume lo que encontraste con la fecha. No pegues los recortes completos.
- Si encontraste algo que vale para sesiones futuras (una decisión, una convención), guárdalo en la memoria automática para que no haga falta buscarlo otra vez.
- Las sesiones duran lo que diga
cleanupPeriodDaysensettings.json(el kit lo pone en 365 días).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

