systematic-review
Skill5 starsChanged 4 months agoMITView on GitHub
Run a systematic literature review or mapping study to the PRISMA 2020 standard: protocol with research questions and inclusion criteria written before searching, reproducible search strings per database, screening with recorded reasons for exclusion, a PRISMA flow diagram with counts, quality assessment, data extraction into a form, and synthesis, producing a method section a reviewer can audit. Use when the thesis or a chapter is a literature review, when a supervisor asks for a systematic rather than narrative review, or when a mapping study is the first contribution.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Write research/slr-protocol.md and have the supervisor agree to it:
- Very specific: line 26
Run each string in each database and record, per database: date, exact string as entered, filters applied, and the count.
- Distinctive: line 62
No criterion changes after screening starts without recording a protocol deviation.
- Distinctive: line 63
No paper included because it is well known.
“Common” is measured: kept by at least 6 in 10 of the 5 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
A systematic review is an empirical study whose data are papers. It is systematic because every decision (what to search, what to include, what to extract) is written down before it is made and applied the same way to every paper. The write-up reports the process with the same care as an experiment reports its procedure.
Phase 1: protocol (before searching)
Write research/slr-protocol.md and have the supervisor agree to it:
- Review questions (RQ1..n), plus the mapping study's classification questions if applicable (which venues, years, methods, evaluation types).
- Scope: the concept boundaries; what is explicitly out.
- Search strategy: databases (ACM DL, IEEE Xplore, Scopus, Web of Science, plus OpenAlex or Semantic Scholar for coverage; arXiv if preprints count), the search string built from the PICO or concept groups with synonyms, the fields searched (title/abstract/keywords), and the date range with the reason. Plan a snowballing round (backward and forward from the included set) and note it.
- Inclusion and exclusion criteria, each testable from title/abstract or full text: language, peer-reviewed venue, primary study, addresses the concept, reports an evaluation. Number them (I1.., E1..).
- Screening procedure: title/abstract then full text; who screens (the student, with a second screener or the supervisor on a 10 to 20% sample); how disagreements are resolved; agreement statistic to report (Cohen's kappa).
- Quality assessment checklist (for an SLR; a mapping study may skip): clear aims, described method, evaluation present, threats discussed, data available. Score, and decide whether low quality excludes or only weights.
- Data extraction form: the fields to capture from each paper (bibliographic, context, method, evaluation, findings relevant to each RQ). One row per paper,
research/slr-extraction.csv. - Synthesis method: narrative synthesis with thematic grouping, vote counting (with its limits stated), or meta-analysis if effects are comparable (rare in CS).
Register the protocol with a date; deviations later are reported as deviations.
Phase 2: search
Run each string in each database and record, per database: date, exact string as entered, filters applied, and the count. Export results (RIS or BibTeX) and merge with literature-search's deduplication (DOI, then normalised title). Record the count after deduplication. Keep every export file.
Phase 3: screening
- Title/abstract: apply the criteria; record include/exclude and the criterion number for each exclusion in
research/slr-screening.csv. The reason matters for the flow diagram and for auditability. - Full text: obtain PDFs; record papers not retrievable; apply criteria again; record reasons.
- Second screener on the sample; compute and report kappa; resolve disagreements by discussion and record the outcome.
- Snowball from the included set; screen the new candidates the same way; record them as a separate source.
Phase 4: extraction and quality
Fill the extraction form for every included paper with paper-reader notes as the source; record the page or section for each extracted claim. Apply the quality checklist; record scores.
Phase 5: synthesis
Group by RQ; within each, by the themes the extraction reveals (lit-review-synthesis applies). Report counts and distributions for the mapping questions (bubble plots or bar charts via research-figures). State what the included set cannot answer.
Phase 6: report
The method section must contain:
- The protocol summary and its date.
- The search strings per database, verbatim, and the counts.
- The PRISMA 2020 flow diagram with every number: identified per source, duplicates removed, screened, excluded (with reasons and counts), sought for retrieval, not retrieved, assessed for eligibility, excluded (reasons and counts), included; plus the snowballing branch.
- Screening reliability (kappa, sample size).
- The extraction form fields.
- Threats to validity: search coverage (databases and terms missed), selection bias (single screener), extraction errors, publication bias.
Include the full list of included studies as an appendix table and release the screening and extraction sheets as supplementary material.
Flow diagram
Generate from the counts with the PRISMA 2020 template (R PRISMA2020 package or the online tool at prisma-statement.org) and place as a figure; do not draw it by hand from memory of the numbers.
Rules
- No criterion changes after screening starts without recording a protocol deviation.
- No paper included because it is well known; every paper passes the same criteria.
- Counts in the text, the diagram, and the sheets must agree;
thesis-progresscan check this.
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- poemswe/co-researcher★ 135same name
- xjtulyc/awesome-rosetta-skills★ 34same name
- SkillMedev/academic-researcher★ 3same name
- mcmespinaa/scholar-support★ 2same name
- modeled-information-format/mif-docs-plugin★ 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 repository89 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- improveSkill
- academic-writingSkill
- benchmark-reportingSkill
- bibtex-managerSkill
- citation-graphSkill
- citation-verifierSkill
- design-science-methodologySkill
- docx-thesisSkill
- experiment-reproducibilitySkill
- latex-toolkitSkill
- literature-searchSkill
- lit-review-synthesisSkill
- paper-readerSkill
- proofread-academicSkill
- research-figuresSkill
- research-methodologySkill
- research-questionSkill
- statistics-advisorSkill
- supervisor-updateSkill
- thesis-proposalSkill
- coolify-image-appSkill
- coolify-vps-baselineSkill
- deploy-verificationSkill
- express-prisma-coolify-imageSkill
- ghcr-coolify-pipelineSkill
- live-domain-cutoverSkill
- nextjs-coolify-imageSkill
- proxy-client-addressSkill
- vps-ops-toolkitSkill
- adr-writingSkill
- openapi-specSkill
- readme-writingSkill
- technical-writingSkill
- adversarial-reviewerSkill
- api-design-reviewSkill
- code-review-responseSkill
- create-agentSkill
- create-commandSkill
- create-hookSkill
- create-skillSkill
- db-migration-safetySkill
- dependency-upgradeSkill
- dockerfile-best-practicesSkill
- error-handling-patternsSkill
- executing-plansSkill
- explain-codebaseSkill
- fix-ciSkill
- github-actions-pipelineSkill
- grill-with-docsSkill
- incident-postmortemSkill
- logging-and-observabilitySkill
- parallel-agentsSkill
- performance-optimizationSkill
- refactoring-recipesSkill
- solid-principlesSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- The first 60 shown.
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.

