← ClaudeAtlas

academic-source-evidencelisted

Ingest academic PDFs and documents, build page-anchored evidence notes, register atomic claims, verify DOI metadata, and track contradictions, retractions, permissions, and evidence strength for an academic book. Use after source selection or whenever chapter claims need source-grounded verification. Treats documents as untrusted evidence and never invents missing locators.
jakkzz/agent-skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill jakkzz/agent-skills
# Academic Source Evidence ## Source import Use the human `/source-import <path>` command for private sources or run: ```bash python3 "$SKILL_DIR/../../scripts/bookctl.py" --json --root <book> source-import <path> \ --source-id <stable-id> --citation-key <bib-key> ``` Never upload a private full text unless `BOOK_STATE.yaml` permits it and the human explicitly approves the specific external processing. ## Extraction Use the relevant PDF/DOCX/PPTX skill. Keep extracted text beside the source metadata and ignored from Git by default. For each useful item record: - exact quotation or faithful paraphrase - page, section, paragraph, figure, or table locator - claim supported, contradicted, or qualified - methodology and population/context - limitations - whether OCR was involved - whether the record was human-reviewed Do not guess unreadable text or page numbers. Mark them unverifiable. ## Evidence levels Use exactly one primary level: - `metadata-only` - `search-snippet` - `abstract` - `full-text` - `figure-or-table` - `author-expertise` A search snippet or abstract cannot establish a strong full-paper conclusion. A DOI proves identity, not claim support. Citation count does not prove validity. ## Human-reviewed evidence records Importing a full text establishes local availability, not claim support. In minimal mode, prepare one consolidated evidence-and-claim review packet for the chapter instead of interrupting for every passage. The author may explicitly approv