willoscar/section-bindings
| Bind papers to chapter-level sections first, writing `outline/section_bindings.jsonl` and `outline/section_binding_report.md`.
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill section-bindings
Always read:
references/overview.mdUse scripts/run.py only for deterministic binding and report materialization:
papers/core_set.csv as the authoritative paper pooloutline/chapter_skeleton.yml as the chapter contractpapers/papers_dedup.jsonl when available for richer metadatapapers/core_set.csvoutline/chapter_skeleton.ymlpapers/papers_dedup.jsonloutline/section_bindings.jsonloutline/section_binding_report.mdassets/output_contract.jsonuv run python .codex/skills/section-bindings/scripts/run.py --workspace <workspace>--workspace <dir>: workspace containing the core set and chapter skeleton--unit-id <id>: optional harness metadata--inputs <semicolon-separated>: optional override from UNITS.csv--outputs <semicolon-separated>: optional output override; defaults are outline/section_bindings.jsonl and outline/section_binding_report.md--checkpoint <C*>: optional harness metadatauv run python .codex/skills/section-bindings/scripts/run.py --workspace <workspace> --inputs 'papers/core_set.csv;outline/chapter_skeleton.yml;papers/papers_dedup.jsonl' --outputs 'outline/section_bindings.jsonl;outline/section_binding_report.md'Take willoscar/section-bindings from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.