search
Skill23 starsChanged 10 months agoMITView on GitHub
This skill should be used when the user says "search memories", "find in memories", "grep mnemonic", "look for memory", "deep search", "synthesize knowledge", or asks questions like "what do we know about X". Provides progressive disclosure and enhanced iterative search with synthesis.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- beCyborg/jadlis-searchtheir own version, first seen Nov 8, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- Mahashwetha/Job-search-email-system-claudetheir own version, first seen Nov 5, 2026
- denolfe/dotfilestheir own version, first seen Nov 2, 2026
- Arcadia-1/virtuoso-bridge-litetheir own version, first seen Nov 1, 2026
- jav-ed/skill_Managtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use fetch, export and 9 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.
jtfasulo7Skillfetch
Use this skill when the user wants to retrieve a URL without a full browser session: fetch HTML or JSON from static pages, inspect status codes or headers, follow redirects, or get page source for simple scraping. Prefer it over a browser when JavaScript rendering and page interaction are not needed. Supports proxies and redirect control.
Also in 3 projects that use this
soilmassSkillexport
Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.
Also in 4 projects that use this
rogue-dev-studioSkillmonitoring
Claude monitoring and usage tracking tools (UV, claude-monitor, claude-usage-cli). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `monitoring` work when listed in TEAM.yaml or explicitly requested.
Also in 3 projects that use this
DockerSkillwrite
Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.
Also in 3 projects that use this
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 4 projects that use this
wrsmith108Skilldocker
Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.
Also in 3 projects that use this
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- anthropics/knowledge-work-plugins★ 35ksame name
- exa-labs/exa-mcp-server★ 5.2ksame name
- browserbase/agent-browse★ 3.7ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
- Muuuun/luxas★ 1.2ksame name
- Arcadia-1/virtuoso-bridge-lite★ 1ksame name
- ZimoLiao/scholaraio★ 585same name
- BlockRunAI/blockrun-mcp★ 389same name
- project-numina/numina-lean-agent★ 279same name
- brightdata/skills★ 270same name
44 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 repository9 other files it gives its agents.
- blackboardSkill
- coreSkill
- custodianSkill
- formatSkill
- integrateSkill
- ontologySkill
- qmd-reindexSkill
- qmd-setupSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 47 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run /mnemonic:list --namespaces to see available namespaces from loaded ontologies.
- Very specific: line 28
Search and filtering for mnemonic memories.
- Distinctive: line 103
Always start at Level 1. Expand only if needed.
- Very specific: line 115
If @tobilu/qmd is installed (see /mnemonic:qmd-setup):
- Very specific: line 138
After adding memories, run /mnemonic:qmd-reindex to update indexes.
- Distinctive: line 151
Use when queries span multiple namespaces or need comprehensive coverage.
“Common” is measured: kept by at least 6 in 10 of the 47 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- BEGIN MNEMONIC PROTOCOL -->Memory
Search first: /mnemonic:search {relevant_keywords}
Capture after: /mnemonic:capture {namespace} "{title}"
Run /mnemonic:list --namespaces to see available namespaces from loaded ontologies.
<!-- END MNEMONIC PROTOCOL -->Mnemonic Search Skill
Search and filtering for mnemonic memories.
Trigger Phrases
- "search memories", "find in memories", "grep memories", "search mnemonic"
- "deep search memories", "comprehensive memory search", "synthesize knowledge about"
Core Search Patterns
By Namespace
rg "^namespace: _semantic/decisions" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -lBy Tag
# Single tag
rg -l "^ - architecture" ${MNEMONIC_ROOT}/ --glob "*.memory.md"
# Multiple tags (AND)
rg -l "^ - architecture" ${MNEMONIC_ROOT}/ --glob "*.memory.md" | xargs rg -l "^ - database"By Type
rg "^type: semantic" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -l
rg "^type: episodic" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -l
rg "^type: procedural" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -lBy Date
rg "^created: 2026-01" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -lBy Title
rg -i '^title: ".*auth.*"' ${MNEMONIC_ROOT}/ --glob "*.memory.md" -lBy Confidence
rg "confidence: 0\.9" ${MNEMONIC_ROOT}/ --glob "*.memory.md" -lFull-Text
rg -i "search term" ${MNEMONIC_ROOT}/ --glob "*.memory.md"Combined: Namespace + Text
rg "database" ${MNEMONIC_ROOT} --path "*/_semantic/decisions/" --glob "*.memory.md"Recent Files
find ${MNEMONIC_ROOT} -name "*.memory.md" -mtime -7Progressive Disclosure Protocol
Always start at Level 1. Expand only if needed.
| Level | What | How |
| 1 (start here) | Titles only | rg -l "pattern" ${MNEMONIC_ROOT}/ --glob "*.memory.md" then extract ^title: |
| 2 | Frontmatter + summary | Read first ~50 lines of matched files |
| 3 | Full detail | Read entire memory file |
Semantic Search (requires qmd)
If @tobilu/qmd is installed (see /mnemonic:qmd-setup):
# BM25 keyword search (ranked)
qmd search "authentication middleware" -n 10
# Semantic vector search (meaning-based)
qmd vsearch "how do we handle user sessions" -n 10
# Hybrid search (BM25 + vector combined)
qmd query "authentication patterns" -n 10
# Scope to collection
qmd search "auth" -c mnemonic-zircote| Tool | Best For | Requires |
rg | Exact strings, regex, frontmatter fields | Nothing |
qmd search | Ranked keyword search, typo-tolerant | qmd update |
qmd vsearch | Conceptual/meaning-based queries | qmd embed |
qmd query | Best overall recall, combines both | Both |
After adding memories, run /mnemonic:qmd-reindex to update indexes.
Enhanced Search (Iterative with Synthesis)
For complex or multi-faceted queries:
- Initial search with user's query
- Analyze results for gaps
- Iterative refinement (up to 3 rounds via Task tool with
mnemonic-search-subcallagent) - Synthesize findings into a coherent answer with source citations
Use when queries span multiple namespaces or need comprehensive coverage.
Output Format
## Synthesized Answer
{Answer drawing from all found memories}
### Sources
| Memory | Namespace | Relevance |
|--------|-----------|-----------|
| [[memory-id]] title | namespace | High/Medium |
### Gaps
- {Topics where no memories were found}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.

