run-paper-reading-workflow

Orchestrates a resumable multi-phase workflow converting academic papers into bilingual Obsidian workspaces.

4|Updated May 20, 2024
One-click install
npx skills add https://github.com/SpreadZhao/spreadconfig --skill run-paper-reading-workflow-spreadzhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-paper-reading-workflow
Source: https://github.com/SpreadZhao/spreadconfig/tree/main/plugins/paper-reading-workbench/skills/run-paper-reading-workflow
Command: npx skills add https://github.com/SpreadZhao/spreadconfig --skill run-paper-reading-workflow-spreadzhao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Deep-reading an academic paper involves many disconnected steps—ingestion, segmentation, translation, question answering, and publication—that are hard to track and easy to lose when a session ends. This Skill turns the whole process into a single resumable, file-backed workflow where every phase, question, and edit is recorded on disk. ## Core Features & Use Cases - Resumable Workspace: Creates one self-contained folder per paper with a workflow state file, so an interrupted reading session can resume from the last validated phase instead of starting over. - Role-Based Pipeline: Coordinates persistent Reader, Answerer, and Writer roles that read chunks sequentially, research questions, and integrate answers into a bilingual publication at precise locations. - Validation & Traceability: Ships scripts that initialize the workspace and validate chunk coverage, question ledgers, Writer placement records, and portable links after every phase boundary. - Use Case: A graduate student drops a PDF of a dense machine-learning paper into the workflow and receives a complete bilingual Obsidian vault with chunk notes, answered questions, a concept glossary, and a publication-ready bilingual document. ## Quick Start Use the run-paper-reading-workflow skill to deeply read the attached paper PDF and build a bilingual Obsidian workspace for it.

Frequently Asked Questions about run-paper-reading-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn an academic paper PDF into an Obsidian vault?

Run the workflow with the paper title and PDF path; the init script creates a self-contained folder with source, chunks, reading notes, and publication directories. The pipeline then ingests, segments, reads, and publishes a bilingual document inside that folder.

How do I resume an interrupted paper reading session?

Re-run the initialization script with the same title and output folder; it detects the existing workflow.json marker and resumes safely. The workflow continues from the first incomplete phase, trusting validated files over chat memory.

What input formats does the paper reading workflow accept?

It accepts PDF files, URLs, DOI or arXiv pages, HTML, Markdown, and plain text inputs. Local files are copied into the workspace with a SHA-256 hash recorded, while URLs are stored as references in the source metadata.

Does the workflow validate that the whole paper was actually read?

Yes. The validation script checks that chunks form an exact ordered partition of all source blocks, that every question has a Writer placement record, and that no blocking questions remain. Final validation also verifies links and assets stay portable.

What happens to questions that cannot be answered from the paper?

Deferred questions are revisited after the final chunk, and irreducible ones are classified as open-research or unanswerable rather than being forced into fake answers. Every question ID must reach a final status before completion.

Can I move the generated paper folder into my existing Obsidian vault?

Yes. The workspace uses relative Markdown links and paper-scoped IDs in wikilinks so the folder stays portable. The validator rejects absolute paths and broken links to guarantee the folder works after being moved.