archive-researcher
Skill2 starsChanged 6 months agoMITView on GitHub
Deep-search Claude-Mem archive history using the search -> ids -> details workflow.
In this repository16 other files it gives its agents.
- algorithmic-artSkill
- 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-personal-dataSkill
- search-webSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill when the agent needs historical technical context from Claude-Mem that is too detailed for the local truth layer alone.
- Distinctive: line 15
Search for candidate observations.
≈ “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
archive-researcher
Use this skill when the agent needs historical technical context from Claude-Mem that is too detailed for the local truth layer alone.
The skill follows Claude-Mem's token-efficient pattern:
- Search for candidate observations.
- Extract the relevant IDs.
- Fetch full observation details only for those IDs.
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.