evidence-research
Skill0 starsChanged yesterdayMITView on GitHub
Use when the user asks to compare options, research a market or tool, or pick a solution under constraints - "compare", "do research", "research", "deep research", "what to choose", "find a solution for", "which bank did this", "are they alive", "find links and back them up in a table", "find the best settings" - whether the subject is tech, banking, pricing, a purchase or a trip.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- loootai/reverse-engineertheir own version, first seen Nov 1, 2026
- BaoBao1996121/crazy-harnesstheir own version, first seen Oct 20, 2026
- RizwanZafaris/product-manager-OStheir own version, first seen Sep 3, 2026
- CN-WenYu/skillstheir own version, first seen Sep 2, 2026
- badgids/Story-Film-Skillstheir own version, first seen Aug 19, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- badgids/Story-Film-Skills★ 4same name
- RizwanZafaris/product-manager-OS★ 4same name
- CN-WenYu/skills★ 3same name
- loootai/reverse-engineer★ 1same name
- BaoBao1996121/crazy-harness★ 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.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- global/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-qualitySkill
- blockersSkill
- changesSkill
- codex-orchestrationSkill
- context-resumeSkill
- copy-checkSkill
- debug-profileSkill
- healthSkill
- project-initSkill
- relaySkill
- reportSkill
- shipSkill
- spec-analyzeSkill
- spec-auditSkill
- spec-dispatchSkill
- spec-nextSkill
- spec-planSkill
- ui-checkSkill
- work-statusSkill
The file
Files
evidence-research: a choice on checked facts
The result is a recommendation you can use right away: the options fit the user's constraints, every fact has a source and a date. General reasoning ("many banks adopt AI") is not a result.
Order
- Criteria. From the request and the context write out the constraints: budget, city, deadlines, stack, jurisdiction, "free", the number of options. Decide what is missing yourself and note it in the report, do not ask.
- Search. Primary sources: the product site, documentation, pricing, official news, registries. Reviews and aggregators only as a hint where to look.
- Specifics. A named product, company, model, feature, price, address, time. "Bank X launched Y in <month, year>", not "banks use".
- Freshness. For a price, availability, a schedule and "is the project alive", the check date. Signs of life: the last release or news, activity, whether the site works.
- Filtering. An option that violates a constraint does not get into the table. It can be mentioned in one line, why it was dropped.
- Comparison in a table by the criteria from step 1. The source link goes in the row, not in a list at the end.
- Recommendation. One option and why. Alternatives if a choice was asked for or if the leader depends on a condition.
- Unknowns. What could not be confirmed and what can only be checked in person.
No internet. First use the available official documents, cache and history; give the date of the source itself. For a price, availability, a schedule and activity mark "freshness unknown"; do not pass off an old price or activity as current. Do the rest of the analysis on the available data, make the recommendation conditional: what to choose if the unconfirmed conditions hold. Do not stop the whole task for lack of network and do not demand actions from the user while there are available sources and useful conclusions.
Answer form
Criteria: <list; decisions made without you>
<table: option | key parameters | price/availability on the date | source>
Recommendation: <option> — <why, 1-2 sentences>
Not confirmed: <facts without a source or needing a personal check>Size fits the task: for an everyday question a table of 3-5 rows, for work research as requested. Create a document only if asked.
Mistakes
| Thought | What to do |
| "I will describe the market trends" | Named players and their features are needed |
| "The price was this last year" | Check it for today or mark it unchecked |
| "The platform is on the list, so it fits" | Check whether it is alive and popular |
| "I will give 10 options to choose from" | As many as asked; by default the single best one |
| "I will attach the sources at the end" | The source next to the fact |
| "It will surely work" | Separate what is checked from what must be tried in person |
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.

