search-personal-data
Skill2 starsChanged 6 months agoMITView on GitHub
Search local files using hybrid semantic and keyword retrieval (ChromaDB + Whoosh). Falls back to recursive grep when the index is unavailable. Use when the user wants to find information in their local documents.
In this repository16 other files it gives its agents.
- algorithmic-artSkill
- archive-researcherSkill
- browser-searchSkill
- claude-mem-clientSkill
- compose-emailSkill
- create-calendar-eventSkill
- evolve-coreSkill
- evolve-memorySkill
- index-filesSkill
- install-packageSkill
- manage-personaSkill
- merge-files-recursivelySkill
- recursive-mergeSkill
- repo-summarizerSkill
- sandboxSkill
- search-webSkill
The file
Files
search-personal-data
Two-tier search strategy:
- Hybrid retrieval (preferred) — semantic vector search via ChromaDB combined with exact keyword matching via Whoosh, merged and ranked.
- Grep fallback — recursive file scan when no index is available.
Usage
Call search_personal_data(query, directory="", max_results=10).
Implementation
Logic lives in scripts/search_personal_data.py.
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.