- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill literature-research -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill literature-research -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill literature-research -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill literature-research -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/fcakyon/labrat/tree/HEAD/plugin/skills/literature-researchFrom the publisher
You are helping a researcher conduct systematic literature research. Follow this methodology to ensure thorough, accurate coverage.
Before searching:
Use multiple search strategies in order:
Use Paper Search CLI. Follow paper search setup if it is missing.
paper-search search 'object detection' -s fast -n 5
paper-search search 'object detection' -s arxiv,crossref -n 5
Inspect the JSON errors field and retain each paper's source ID and URL. Report unavailable providers rather than treating errors as an empty literature search. Vary search terms to catch different framings of the same concept. Use web search for proceedings and sources the CLI cannot access, and check Google Scholar, Semantic Scholar, and arXiv. Look for survey papers that map the area.
From seed papers or initial results:
paper-search tool get_citing_papers <doi>paper-search tool get_referenced_papers <doi>Organize found papers into a structured taxonomy:
| Paper | Year | Venue | Approach | Key Result | Code? | Relevance |
|-------|------|-------|----------|-----------|-------|-----------|
Group by methodology or approach type, not chronologically.
Map what exists vs. what's missing:
| Approach | Representative Papers | Coverage | Gap? |
|----------|----------------------|----------|------|
For each identified gap, verify it's real:
Rate confidence: HIGH (every box above checked, clearly missing), MEDIUM (niche venues unchecked), LOW (limited search, gap may exist under different terminology).
Produce a structured overview of the field. Title it Gap Analysis: [Topic] when the user asked for a gap analysis.
## Literature Research: [Topic]
### Research Landscape
[2-3 sentence overview of the research area]
### Paper Table
[Step 3 table: year, venue, approach, results, code availability]
### Coverage Table
[Step 4 table]
### Identified Gaps
| Gap | Confidence | Evidence of Absence | Why It Matters |
|-----|-----------|---------------------|---------------|
### Recommended Readings
[Top 5-10 most relevant papers for the user's specific work]
### Candidate Citations
[BibTeX entries for papers worth citing, verified per Citation Integrity]
Verify every paper you mention with check 5 (Citations) in paper-check before presenting it, including any result numbers you quote. Flag any detail you cannot confirm rather than guessing.
>
---name: literature-researchdescription: >---# plugin/skills/literature-research/SKILL.mdFAQ
Download plugin/skills/literature-research/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/fcakyon/labrat.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.