3b6456cd5d641e8a947594eb9ab67a74b86e6e72
- Author
- TheEdgeOfRage <git@theedgeofrage.com>
- Committer
- TheEdgeOfRage <git@theedgeofrage.com>
- Date
Message
Diff
This diff is truncated to protect this page.
1diff --git a/dot_agents/skills/qmd/SKILL.md b/dot_agents/skills/qmd/SKILL.md
2deleted file mode 100644
3index de910987c35e99fc0024863f7fbbe5040974387b..0000000000000000000000000000000000000000
4--- a/dot_agents/skills/qmd/SKILL.md
5+++ /dev/null
6@@ -1,125 +0,0 @@
7----
8-name: qmd
9-description: Search markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information in local files.
10-license: MIT
11-compatibility: Requires qmd CLI
12-metadata:
13-author: tobi
14-version: "2.0.0"
15-allowed-tools: Bash(qmd:\*)
16----
17-
18-# QMD - Quick Markdown Search
19-
20-Local search engine for markdown content.
21-
22-## Status
23-
24-!`qmd status 2>/dev/null || echo "Not installed: npm install -g @tobilu/qmd"`
25-
26-### Query Types
27-
28-| Type | Method | Input |
29-| ------ | ------ | ------------------------------------------- |
30-| `lex` | BM25 | Keywords — exact terms, names, code |
31-| `vec` | Vector | Question — natural language |
32-| `hyde` | Vector | Answer — hypothetical result (50-100 words) |
33-
34-### Writing Good Queries
35-
36-**lex (keyword)**
37-
38-- 2-5 terms, no filler words
39-- Exact phrase: `"connection pool"` (quoted)
40-- Exclude terms: `performance -sports` (minus prefix)
41-- Code identifiers work: `handleError async`
42-
43-**vec (semantic)**
44-
45-- Full natural language question
46-- Be specific: `"how does the rate limiter handle burst traffic"`
47-- Include context: `"in the payment service, how are refunds processed"`
48-
49-**hyde (hypothetical document)**
50-
51-- Write 50-100 words of what the _answer_ looks like
52-- Use the vocabulary you expect in the result
53-
54-**expand (auto-expand)**
55-
56-- Use a single-line query (implicit) or `expand: question` on its own line
57-- Lets the local LLM generate lex/vec/hyde variations
58-- Do not mix `expand:` with other typed lines — it's either a standalone expand query or a full query document
59-
60-### Intent (Disambiguation)
61-
62-When a query term is ambiguous, add `intent` to steer results:
63-
64-```json
65-{
66- "searches": [{ "type": "lex", "query": "performance" }],
67- "intent": "web page load times and Core Web Vitals"
68-}
69-```
70-
71-Intent affects expansion, reranking, chunk selection, and snippet extraction. It does not search on its own — it's a steering signal that disambiguates queries like "performance" (web-perf vs team health vs fitness).
72-
73-### Combining Types
74-
75-| Goal | Approach |
76-| --------------------- | ----------------------------------------------------- |
77-| Know exact terms | `lex` only |
78-| Don't know vocabulary | Use a single-line query (implicit `expand:`) or `vec` |
79-| Best recall | `lex` + `vec` |
80-| Complex topic | `lex` + `vec` + `hyde` |
81-| Ambiguous query | Add `intent` to any combination above |
82-
83-First query gets 2x weight in fusion — put your best guess first.
84-
85-### Lex Query Syntax
86-
87-| Syntax | Meaning | Example |
88-| ---------- | ------------ | ---------------------------- |
89-| `term` | Prefix match | `perf` matches "performance" |
90-| `"phrase"` | Exact phrase | `"rate limiter"` |
91-| `-term` | Exclude | `performance -sports` |
92-
93-Note: `-term` only works in lex queries, not vec/hyde.
94-
95-### Collection Filtering
96-
97-```json
98-{ "collections": ["docs"] } // Single
99-{ "collections": ["docs", "notes"] } // Multiple (OR)
100-```
101-
102-Omit to search all collections.
103-
104-## CLI
105-