sota-writerlisted

Write structured State-of-the-Art (SOTA) reviews / literature reviews for academic research projects with **zero hallucinated citations**. Activate this skill whenever the user wants to write, update, or expand a SOTA. Triggers (FR + EN) : "écris un SOTA", "état de l'art sur", "revue de littérature", "mise à jour SOTA", "survey sur", "nouveau SOTA", "write a SOTA on", "literature review on", "state-of-the-art review", "/paper-trail:new-sota". **MANDATORY** : this skill enforces an INVERTED workflow (research first → read validated PDFs → write). It REFUSES to write from memory to prevent the kind of citation hallucinations (inverted attributions, fabricated quotes) that led to retracted papers in the past. Make sure to use this skill whenever any SOTA work is requested, even if the user doesn't explicitly say "use sota-writer".
roomi-fields/paper-trail · ★ 3 · AI & Automation · score 76

Install: claude install-skill roomi-fields/paper-trail

# Skill : SOTA Writer (research-first, anti-hallucination) ## Why this skill exists Citation hallucinations in academic writing are systemic when the author writes from memory and looks up sources afterward. They include inverted attributions ("X proved Y" when X proved ¬Y), fabricated quotes (text in quotation marks that doesn't appear in the cited source), wrong attributions (citing the wrong author for a known result), and confusion between similar-named papers (homonymy). The plugin paper-trail exists because a retracted paper in 2026-02 contained 12 such errors, signaled by the misrepresented author themselves. This skill encodes the **inverted workflow** : research → read → write. Slower in appearance, faster in practice : no post-submission audit, no remediation, no reviewer embarrassment. ## Scope - **Vault root** : `$RESEARCH_VAULT_PATH` (resolved via the adapter, default obsidian) - **Registry** : `$RESEARCH_REGISTRY_PATH/refs/*.md` (one `.md` file per ref with YAML frontmatter) - **SOTA output location** : resolved via `adapter.sota_output_path(topic_slug)` ## The supreme rule **No claim in a SOTA without pointing to the notes body of a ref file in state `page1_validated` (or higher).** If I want to write X but no source supports X → either I find one, or I don't write X. No rhetorical rephrasing to "keep" an unsourced claim. ## Mandatory 4-phase workflow ``` A. EXHAUSTIVE RESEARCH ├─ paper-search MCP (search_papers multi-source, 22 platforms)