qmd
Skill166 starsChanged 5 months agoMITView on GitHub
Search vault notes by keyword or meaning. Args: <query>. Uses QMD (lex, vec, deep search).
- Installs packages
- Sends data out
24 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- joinQuantish/lean-memorytheir own version, first seen Nov 16, 2026
- compozy/compozyedited, first seen Nov 13, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
- droxey/skillstheir own version, first seen Nov 8, 2026
- Liang-MH/skillstheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemonedited, first seen Nov 6, 2026
Used with
Projects with it also use agent-browser, vercel-react-best-practices and 1 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.
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 4 projects that use this
VercelSkillvercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- compozy/compozy★ 2.9k78% same
- ManceRayder42/jarvis-os★ 564% same
- FelipeAngeli/skills★ 278% same
- pankaj-mahaur/Agent-Daemon★ 068% same
Wrote their own version · 20
- tobi/qmd★ 31ksame name
- breferrari/obsidian-mind★ 5.4ksame name
- levineam/qmd-skill★ 703same name
- pedronauck/skills★ 655same name
- SAP/e-mobility-charging-stations-simulator★ 232same name
- ckorhonen/claude-skills★ 17same name
- iagocavalcante/claude-turbo-search★ 16same name
- superuser-pal/awesome-second-brain★ 14same name
- Yassimba/loom★ 13same name
- docxology/codomyrmex★ 11same name
10 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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- vault-healthSkill
- workspace-modeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Write 50-100 words of what the *answer* looks like
- Distinctive: line 56
Use the vocabulary you expect in the result
- Very specific: line 59
Use a single-line query (implicit) or expand: question on its own line
- Very specific: line 61
Do not mix expand: with other typed lines — it's either a standalone expand query or a full query document
“Common” is measured: kept by at least 6 in 10 of the 22 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
QMD - Quick Markdown Search
Local search engine for markdown content.
Status
!qmd status 2>/dev/null || echo "Not installed: npm install -g @tobilu/qmd"
MCP: query
{
"searches": [
{ "type": "lex", "query": "CAP theorem consistency" },
{ "type": "vec", "query": "tradeoff between consistency and availability" }
],
"collections": ["docs"],
"limit": 10
}Query Types
| Type | Method | Input |
lex | BM25 | Keywords — exact terms, names, code |
vec | Vector | Question — natural language |
hyde | Vector | Answer — hypothetical result (50-100 words) |
Writing Good Queries
lex (keyword)
- 2-5 terms, no filler words
- Exact phrase:
"connection pool"(quoted) - Exclude terms:
performance -sports(minus prefix) - Code identifiers work:
handleError async
vec (semantic)
- Full natural language question
- Be specific:
"how does the rate limiter handle burst traffic" - Include context:
"in the payment service, how are refunds processed"
hyde (hypothetical document)
- Write 50-100 words of what the answer looks like
- Use the vocabulary you expect in the result
expand (auto-expand)
- Use a single-line query (implicit) or
expand: questionon its own line - Lets the local LLM generate lex/vec/hyde variations
- Do not mix
expand:with other typed lines — it's either a standalone expand query or a full query document
Combining Types
| Goal | Approach |
| Know exact terms | lex only |
| Don't know vocabulary | Use a single-line query (implicit expand:) or vec |
| Best recall | lex + vec |
| Complex topic | lex + vec + hyde |
First query gets 2x weight in fusion — put your best guess first.
Lex Query Syntax
| Syntax | Meaning | Example |
term | Prefix match | perf matches "performance" |
"phrase" | Exact phrase | "rate limiter" |
-term | Exclude | performance -sports |
Note: -term only works in lex queries, not vec/hyde.
Collection Filtering
{ "collections": ["docs"] } // Single
{ "collections": ["docs", "notes"] } // Multiple (OR)Omit to search all collections.
Other MCP Tools
| Tool | Use |
get | Retrieve doc by path or #docid |
multi_get | Retrieve multiple by glob/list |
status | Collections and health |
CLI
qmd query "question" # Auto-expand + rerank
qmd query $'lex: X\nvec: Y' # Structured
qmd query $'expand: question' # Explicit expand
qmd search "keywords" # BM25 only (no LLM)
qmd get "#abc123" # By docid
qmd multi-get "journals/2026-*.md" -l 40 # Batch pull snippets by glob
qmd multi-get notes/foo.md,notes/bar.md # Comma-separated list, preserves orderHTTP API
curl -X POST http://localhost:8181/query \
-H "Content-Type: application/json" \
-d '{"searches": [{"type": "lex", "query": "test"}]}'Setup
npm install -g @tobilu/qmd
qmd collection add ~/notes --name notes
qmd embedDoes 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.

