quick-search
Skill109 starsChanged 38 days agoMITView on GitHub
Fast knowledge base retrieval - single FAISS search + graph connections, no subagents or LLM orchestration
In this repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- ai-crystallizeSkill
- analyze-kbSkill
- auto-discoverySkill
- benchmark-memorySkill
- brain-mergeSkill
- changelog-protocolSkill
- coherence-sweepSkill
- compute-lifecycleSkill
- create-articleSkill
- create-explanatory-imageSkill
- decideSkill
- deep-researchSkill
- detect-tensionsSkill
- dialecticSkill
- domain-watchSkill
- elicitation-techniquesSkill
- epistemic-classificationSkill
- epub-chapter-extractorSkill
- extract-document-insightsSkill
- extract-insightsSkill
- find-connectionsSkill
- first-runSkill
- get-perspective-onSkill
- get-youtube-transcriptSkill
- git-commit-pushSkill
- graduate-insightsSkill
- incubation-loopSkill
- ingest-sourceSkill
- insight-capture-formatSkill
- insight-interviewSkill
- integrate-recent-notesSkill
- learn-new-thingsSkill
- manage-reference-dataSkill
- manage-thinking-topicsSkill
- manage-watching-domainsSkill
- multi-format-book-extractorSkill
- nano-banana-image-generatorSkill
- propagate-changeSkill
- reasoning-checksSkill
- recallSkill
- ref-auditSkill
- ref-bridgeSkill
- ref-ingestSkill
- ref-querySkill
- ref-reconcileSkill
- ref-refreshSkill
- refresh-indexSkill
- ref-supersedeSkill
- scheduled-runSkill
- scope-mountSkill
- search-vaultSkill
- self-diagnosticSkill
- start-hereSkill
- synthesize-insightsSkill
- talkSkill
- test-memory-systemSkill
- think-about-itSkill
- update-changelogSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 61
NO subagent spawning: - do everything inline
- Distinctive: line 64
NO spreading activation: - use static mode (faster for simple lookups)
- Distinctive: line 65
Parallel execution: - run search and connections in the same message
- Distinctive: line 66
Maximum 3 tool calls: - search + connections + read top file
- Very specific: line 67
If the user wants deeper analysis, tell them to use /recall or /find-connections
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quick Search
Fastest possible knowledge base retrieval. No subagents, no multi-layer orchestration, no changelogs.
Purpose
Return relevant notes and their graph neighborhood in minimal tool calls. Designed for speed over thoroughness.
Query
$ARGUMENTS
Process
Execute these two commands in parallel (single message, two Bash calls):
# 1. Semantic search (6-14s - the unavoidable cost)
BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_search.sh "$ARGUMENTS" --limit 5 --json
# 2. Graph connections for likely top hit (0.3s - nearly free)
BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_connections.sh "$ARGUMENTS" --json
# read role: lookup (contract: scope-mount) - group the output: your thinking (core) · what you have read (Books / Document Insights); --scope core pins to your own notesThen read the top result file using Read tool.
That's it. Three tool calls. Present results and stop.
Output Format
Keep it brief:
## [Query]
**Top matches:**
1. [[Note Title]] (0.XX) - [one-line summary from content]
2. [[Note Title]] (0.XX) - [one-line summary]
3. [[Note Title]] (0.XX) - [one-line summary]
**Graph neighborhood** (for top hit):
- Outgoing: [[Note]], [[Note]], ...
- Incoming: [[Note]], [[Note]], ...
**Top result content:**
[First ~30 lines of the highest-scoring note]Rules
- NO subagent spawning - do everything inline
- NO changelog creation - this is a read-only lookup
- NO multi-layer expansion - one search, one connection call, done
- NO spreading activation - use static mode (faster for simple lookups)
- Parallel execution - run search and connections in the same message
- Maximum 3 tool calls - search + connections + read top file
- If the user wants deeper analysis, tell them to use
/recallor/find-connections
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.

