DeepPaperNote is:
- a single-skill repository
- designed for deep reading of one paper at a time
- intended to support both Claude Code and Codex
- focused on producing a high-quality Obsidian-oriented paper note
DeepPaperNote is not:
- a multi-paper review framework
- a shallow summary generator
Use the following source-of-truth hierarchy when working in this repository:
- root
SKILL.mdis the canonical workflow definition scripts/andreferences/are part of the reusable coreREADME.mdandREADME.zh-CN.mdare user-facing documentation, not the canonical workflowagents/openai.yamlis the Codex adapter layer; the rootSKILL.mdis the Claude Code skill entrypoint
Adapter layers should stay thin and should not redefine the workflow independently.
Future changes should preserve these product invariants:
- DeepPaperNote handles one paper at a time
- the workflow remains evidence-first
- required stages must not be silently skipped
- weak evidence should fail closed rather than being presented as a full deep read
- figure and table placeholder-first handling remains required
- lint plus final readability review remain required before completion
- Obsidian-first save semantics remain intact
- the paper-local
images/directory remains part of the save protocol - scripts remain deterministic support tools, while paper understanding and final note writing remain model-led
The repository is layered as follows:
SKILL.mdis the canonical workflow definition and the skill entrypoint for both Claude Code and other agentsCLAUDE.mdprovides Claude Code project-level guidance and includesAGENTS.mdvia@AGENTS.mdreferences/stores durable workflow and writing guidancescripts/implements the deterministic pipeline and support utilitiesagents/openai.yamlis the Codex adapterREADME.mdandREADME.zh-CN.mdare user-facing documentation
- user installation, configuration, and onboarding belong primarily in
README.mdandREADME.zh-CN.md scripts/check_environment.pyis a maintenance and troubleshooting utility- DeepPaperNote should not reintroduce a separate public
doctor,setup, orstartskill surface
Common commands for local validation and maintenance:
- install the core runtime dependency with
python3 -m pip install PyMuPDF - install the local development environment with
python3 -m pip install -e '.[dev]' - run the test suite with
python3 -m pytest -q - when checking environment-related problems, use
python3 scripts/check_environment.py
When making meaningful changes:
- run
python3 -m pytest -q - confirm adapters remain aligned with the root
SKILL.md - confirm no wrapper introduces a second conflicting workflow
- confirm legacy public pseudo-commands are not reintroduced
- if packaging files are touched, keep them syntactically valid