deepsearch
Skill2 starsChanged 20 days agoMITView on GitHub
Research current technical facts (API behaviour, versions, pricing, benchmarks) or find prior art before a substantial new build. A single local lookup needs no sweep.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- lza6/claw-code-tingfengtheir own version, first seen Nov 1, 2026
- jcsaaddupuy/badrobotstheir own version, first seen Feb 26, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- lza6/claw-code-tingfeng★ 5same name
- jcsaaddupuy/badrobots★ 1same 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.
In this repository10 other files it gives its agents.
- cards-readmeSkill
- cleanupSkill
- engineer-mindsetSkill
- grill-meSkill
- investigateSkill
- layoutSkill
- presentSkill
- review-prSkill
- sentry-cliSkill
- toolchainSkill
The file
Files
Deep search
Choose depth from the unresolved claim and the cost of being wrong. Existing evidence can settle a small question; open only the channels that claim needs.
- Current API/library behavior, pricing, versions, benchmarks or a sourced comparison: research workflow. Search only applicable channels and prefer official docs/source plus local measurement.
- A substantial new pipeline, training method or system where an existing artifact could change the build: prior-art workflow. Check hard fit requirements before popularity or repository quality.
Label evidence T1 official/source, T2 maintainer issue/changelog, T3 community, T0 recollection. Recollection alone is not evidence. Done when every material claim carries its tier and the reply states which claims remain unverified and what was not searched. A narrow question gets a narrow answer. Public search queries carry public terms only: no credentials, internal hostnames or private data.
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.