# Paper Notes

Write structured notes for each paper in the core set into `papers/paper_notes.jsonl`...

- Repository: https://github.com/WILLOSCAR/research-units-pipeline-skills (517 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-10-05
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill paper-notes -g -a claude-code -y`
Codex: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill paper-notes -g -a codex -y`
Cursor: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill paper-notes -g -a cursor -y`
Gemini CLI: `npx skills add WILLOSCAR/research-units-pipeline-skills --skill paper-notes -g -a gemini-cli -y`

## Description

Write structured notes for each paper in the core set into `papers/paper_notes.jsonl` (summary/method/results/limitations).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Paper Notes

## Triggers & routing

- **Trigger**: paper notes, structured notes, reading notes, 论文笔记, paper_notes.jsonl.
- **Use when**: survey 的 evidence 阶段（C3），已有 `papers/core_set.csv`（以及可选 fulltext），需要为后续 claims/citations/writing 准备可引用证据。


Produce consistent, searchable paper notes that later steps (claims, visuals, writing) can reliably synthesize.

This is still **NO PROSE**: keep notes as bullets / short fields, not narrative paragraphs.

## Load Order

Always read:
- `references/overview.md`
- `references/note_schema.md`

Read by task:
- `references/limitation_taxonomy.md` when writing or reviewing limitations (avoid boilerplate)
- `references/result_extraction_examples.md` when extracting key_results (good vs bad examples)
- `references/source_text_hygiene.md` when result/limitation fields still preserve paper self-narration or author-result wrappers

Machine-readable assets:
- `assets/note_schema.json`, JSONL record schema for validation
- `assets/evidence_tags.json`, evidence bank tagging categories (extensible without code changes)
- `assets/source_text_hygiene.json`, note-field source sentence cleanup policy
- repo-wide `assets/limitation-signals.json`, shared polarity rules for
  distinguishing unresolved constraints from resolved failures or improvements

## Script Boundary

Use `scripts/run.py` only for:
- deterministic scaffold generation from core_set + metadata
- priority selection based on mapping coverage
- evidence bank construction from structured note fields

Do not treat `run.py` as the place for:
- paper-specific limitation prose (use `references/limitation_taxonomy.md` for guidance)
- domain-specific evaluation heuristics hidden in code
- reader-facing narrative text

## Role cards (prompt-level guidance)

The rest: https://github.com/WILLOSCAR/research-units-pipeline-skills/blob/HEAD/.codex/skills/paper-notes/SKILL.md