research-survey
Skill0 starsChanged 8 months agoNo licenceView on GitHub
Build comprehensive, evidence-based research reports from a topic, paper cluster, frontier question, company landscape, or product space, and store the result as a Markdown document. Use when the user wants a structured调研报告, frontier snapshot, deep literature map, company and product landscape, research judgment memo, or a reusable long-form report that goes beyond brief social-media repackaging. Especially relevant for researchers and research teams who need a thorough report first, with clear evidence, arguments, limitations, market context, and open questions.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- tsingyuai/scientifytheir own version, first seen Oct 8, 2026
- EvoScientist/EvoSkillstheir own version, first seen Sep 30, 2026
- KalarisLabs/Skill-Doctortheir own version, first seen Sep 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- tsingyuai/scientify★ 2.2ksame name
- EvoScientist/EvoSkills★ 481same name
- KalarisLabs/Skill-Doctor★ 12same 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
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. 0 are common, 29 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
29
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.