Menu
Count pages per section in a compiled LaTeX paper PDF. Enables PDF bookmarks if disabled, then extracts section titles and page numbers from the PDF outline. Used by law-build after a successful compilation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Compile a LaTeX academic paper with pdflatex. Use when the user asks to build, compile, or check the paper. Also run law-pagecount and law-verify after a successful build.
Run post-build verification checks on a compiled LaTeX paper. Checks for emdashes, undefined references and citations, mid-paragraph bold text, hyphens in prose, and missing appendix cross-references. Use after law-build succeeds.
Write experiment guides for handing off work from agent to human. Use when the user asks what experiments are needed, requests a task list for a student, or when todo.md contains items the agent cannot complete (code execution, data collection, figure generation, hardware access). Produce a concise guide with specific deliverables per experiment: CSV schema, plotting script, and final figure.
Parse reviewer feedback into a structured todo.md revision tracker for academic papers. Use when the user asks to triage reviews, extract actionable items from review comments, or create a revision plan from reviewer feedback. Flags uncertain items for human confirmation.
Create a new academic paper repository with the correct directory structure, venue template, and agent instruction files. Use when the user asks to create a new paper, bootstrap a paper project, start a new submission, or set up a paper repo for a specific venue (NSDI, SIGCOMM, APNet, arxiv).
Prepare a paper for resubmission to a different venue after rejection. Use when the user asks to resubmit, switch venues, or change the target conference. Copies the paper repo, swaps document templates, archives old artifacts, and preserves git history.
Based on SOC occupation classification
| name | law-pagecount |
| description | Count pages per section in a compiled LaTeX paper PDF. Enables PDF bookmarks if disabled, then extracts section titles and page numbers from the PDF outline. Used by law-build after a successful compilation. |
Count pages per section from a compiled paper PDF. This is invoked automatically after law-build succeeds.
If the PDF has no bookmarks (outlines), enable them by running scripts/enable-bookmarks.sh, then trigger a rebuild before counting.
Run scripts/count-pages.sh [paper_root] which uses pikepdf (or pdftk fallback) to extract section titles and page numbers from the PDF outline.
Output the per-section page counts in a readable format:
§1 Introduction — pages 1–2 (1.5 pages)
§2 Background — pages 3–4 (1.2 pages)
After counting, add a note to todo.md:
- [ ] Re-disable PDF bookmarks before submission (enabled by law-pagecount)
And add a note to AGENTS.md if not already present:
<!-- law-pagecount: bookmarks re-enabled for page counting. Re-disable before submission. -->
Only re-disable bookmarks when the user explicitly asks. The user must request it — never do it automatically.
pikepdf (pip install pikepdf) OR pdftkIf neither is installed, report the missing dependency and skip the count.