systematic-review
- Repo stars 13,134
- Author updated Live
- Author repo AutoResearchClaw
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @aiming-lab · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: systematic-review
description: Structured methodology for comprehensive literature review following PRISMA guidelines. Use duri…
category: engineering
runtime: no special runtime
---
# systematic-review output preview
## PART A: Task fit
- Use case: Structured methodology for comprehensive literature review following PRISMA guidelines. Use during literature search and screening stages. Follow PRISMA-like methodology for literature search: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Systematic Review Best Practice” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Structured methodology for comprehensive literature review following PRISMA guidelines. Use during literature search and screening stages. Follow PRISMA-like methodology for literature search: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Systematic Review Best Practice” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Systematic Review Best Practice”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: systematic-review
description: Structured methodology for comprehensive literature review following PRISMA guidelines. Use duri…
category: engineering
source: aiming-lab/AutoResearchClaw
---
# systematic-review
## When to use
- Structured methodology for comprehensive literature review following PRISMA guidelines. Use during literature search a…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Systematic Review Best Practice” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "systematic-review" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Systematic Review Best Practice
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Systematic Review Best Practice
Follow PRISMA-like methodology for literature search:
- Define clear inclusion/exclusion criteria BEFORE searching
- Use multiple databases (Semantic Scholar, arXiv, OpenAlex)
- Search with both broad and narrow queries
- Screen by title/abstract first, then full text
- Extract: method, dataset, metrics, key findings
- Synthesize gaps and opportunities, not just summaries
- Prioritize recent (last 2-3 years) high-citation papers
- Include at least one seminal/foundational paper per sub-topic
Decide Fit First
Design Intent
How To Use It
Boundaries And Review