systematic review

Engineering Community

Skill notes

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

## Systematic Review Best Practice
Follow PRISMA-like methodology for literature search:
1. Define clear inclusion/exclusion criteria BEFORE searching
2. Use multiple databases (Semantic Scholar, arXiv, OpenAlex)
3. Search with both broad and narrow queries
4. Screen by title/abstract first, then full text
5. Extract: method, dataset, metrics, key findings
6. Synthesize gaps and opportunities, not just summaries
7. Prioritize recent (last 2-3 years) high-citation papers
8. Include at least one seminal/foundational paper per sub-topic

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.