sift
Skill1 starsChanged 40 days agoMITView on GitHub
Rank files, functions or grep hits by how worth reading they are for a question, before reading any of them.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- frankieramirez/manatheir own version, first seen Oct 17, 2026
- frankieramirez/ripentheir own version, first seen Sep 8, 2026
- LouPineWays/Loop-Dee-Louptheir own version, first seen Aug 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- frankieramirez/mana★ 1same name
- frankieramirez/ripen★ 0same name
- LouPineWays/Loop-Dee-Loup★ 0same name
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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 11
Run jev sift --query "<the question>" <paths, or .
“Common” is measured: kept by at least 6 in 10 of the 3 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
Decide what to read before reading it. The question is: $ARGUMENTS
- Run
jev sift --query "<the question>" <paths, or . when none were given> --top 8. For a huge tree, narrow first withrg -l <keyword> | jev sift --files-from - --query "<question>", or grade single functions of one big file with--functions. - Each line is
p tokens-to-read path. Read the top entries in order and stop when a file answers the question; never read past a--- budgetmarker without saying why. - Answer with what you found and the files you read, citing
path:line.
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.