literature-search

Name: literature-search
Author: aiming-lab

Writing Community

Repo stars 13,134
Author updated Live
Author repo AutoResearchClaw

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Writing
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，默认拥有全部工具权限。

Output preview literature-search.preview

---
name: literature-search
description: Systematic literature review methodology including search strategy, screening, and synthesis. Us…
category: writing
runtime: no special runtime
---

# literature-search output preview

## PART A: Task fit
- Use case: Systematic literature review methodology including search strategy, screening, and synthesis. Use when conducting literature reviews or writing background sections. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Literature Search Best Practice / Search Strategy Design / Inclusion and Exclusion Criteria” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Systematic literature review methodology including search strategy, screening, and synthesis. Use when conducting literature reviews or writing background sections. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Literature Search Best Practice / Search Strategy Design / Inclusion and Exclusion Criteria” 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.

SKILL.md SKILL.md

---
name: literature-search
description: Systematic literature review methodology including search strategy, screening, and synthesis. Us…
category: writing
source: aiming-lab/AutoResearchClaw
---

# literature-search

## When to use
- Systematic literature review methodology including search strategy, screening, and synthesis. Use when conducting lite…
- 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 “Literature Search Best Practice / Search Strategy Design / Inclusion and Exclusion Criteria” 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.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "literature-search" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Literature Search Best Practice / Search Strategy Design / Inclusion and Exclusion Criteria
  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
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Systematic literature review methodology including search strategy, screening, and synthesis. Use when conducting literature rev…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Literature Search Best Practice”, “Search Strategy Design”, “Inclusion and Exclusion Criteria”, “PRISMA Methodology”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name literature-search directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Literature Search Best Practice / Search Strategy Design / Inclusion and Exclusion Criteria” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.