literature
Literature Skill
Comprehensive academic literature workflow: discover, verify, organise, synthesise. Uses parallel sub-agents to search multiple sources, verify citations, and fetch PDFs concurrently.
Web alternative: a lighter-weight version of this workflow runs at literature.user.com (
packages/literature-workspace/) — keyword/file-upload search across biblio-sources + RefPile, with Sonnet-driven synthesis. Useful for collaborators (CF Access auth) or quick discovery sessions where you don't need vault sync, DOI hard-gating, or pipeline mode. Use the CLI skill when you need verified citations entering a.bibfile or full Phase 5 synthesis with negative-evidence + cross-cluster analysis.
Hard Rules
Existential — block submission
These rules protect against the highest-cost failure modes. Violation invalidates the output.
- Every citation must be verified to exist before inclusion. Never include a paper you cannot find via web search. Hallucinated citations are worse than no citations.
- Every DOI must be programmatically verified before entering any
.bibfile. Sub-agents hallucinate plausible-looking DOIs that resolve to wrong papers (correct journal prefix, wrong suffix). The only reliable verification isscholarly scholarly-verify-doiswith title-matching (Phase 3). A DOI that resolves to a different title is WRONG — treat it the same as a missing DOI. - The narrative synthesis ALWAYS lives at
docs/literature-review/literature_summary.md. Never inpaper/,paper-*/, or any Overleaf-synced directory. Thepaper/directory is LaTeX-only. Markdown files there leak onto Overleaf and pollute the submission folder. Canonical filename:literature_summary.md(never_synthesis.md,synthesis.md, ad-hoc names).
Format — catch in review
More from flonat/claude-research
update-focus
Use when you need to update current-focus.md with a structured session summary.
11project-safety
Use when you need to set up safety rules and folder structures for a research project.
11latex-autofix
Use when you need to compile LaTeX with autonomous error resolution and citation audit.
8pre-submission-report
Use when you need all quality checks run before submission, producing a single dated report.
7process-reviews
Use when you need to process referee comments from a reviews PDF into tracking files.
7code-archaeology
Use when you need to review and understand old code, data, or analysis files.
7