qhjqhj00 name: stat-writing description: End-to-end statistical writing assistant for LaTeX - draft title/abstract/keywords, expand outlines into sections, audit manuscripts, write reviewer reports and response letters, and scaffold book manuscripts. license: CC0-1.0 metadata: author: stat-writing-one-skill version: "3.0" compatibility: Codex (CLI + IDE). Optional scripts require Python 3.
Statistical Writing (One Skill)
This is a single "workbench" skill for statistical manuscripts written in LaTeX.
Guidance is split into focused references under references/. Deterministic checks live in scripts/. Ready-to-use templates live in assets/.
Positioning: Hybrid + JDS profile
Default behavior is journal-agnostic. For Journal of Data Science (JDS), apply the JDS profile:
- Maintain strong literature positioning and explicit novelty.
- Require clean cross-referencing and cleaned BibTeX.
- Prefer vector graphics for figures in the manuscript.
- Enable line numbers for review drafts.
- Include reproducibility artifacts (code/data/supplement) when possible.
When to use this skill
Use this skill when the user wants to:
- Generate compliant front matter (title, abstract, keywords).
- Expand outlines into complete sections in LaTeX.
- Audit a manuscript for structure, style, references, and reproducibility quality.
- Draft reviewer reports.
- Draft point-by-point response letters.
- Scaffold a book manuscript from a chapter plan.
Inputs to ask for (minimal)
Prefer file paths over pasted text.
- Manuscript tasks: root TeX file (for example
main.tex). - Reference checks: BibTeX file(s) (for example
refs.bib). - Response letters: full reviewer/editor comments + revised text if available.
- Reviewer report: manuscript or extended abstract being reviewed.
- Book manuscript: chapter list, audience, tone, and desired notation style.
If details are missing, proceed with placeholders like odo{...} and ask only critical questions.
Output conventions
Unless the user requests otherwise:
- Return LaTeX-ready output.
- For audits: rank issues as HIGH/MED/LOW with concrete fixes.
- For rewrites: include revised text and short change log.
- Never invent results or citations. Use
odo{add citation}orodo{verify result}.
Task routing map
Open only the reference files needed for the task.
- Title:
references/10-title.md - Abstract:
references/11-abstract.md - Keywords:
references/12-keywords.md - Outline to section drafting:
references/60-outline-to-section.md - Introduction:
references/20-introduction.md - Data:
references/21-data.md - Methods:
references/22-methods.md - Simulation (ADEMP):
references/23-simulation.md - Application/Results:
references/24-application.md - Discussion:
references/25-discussion.md - Other sections:
references/30-other-sections.md - General style/storyline:
references/31-general-style.md - English pitfalls:
references/32-english.md - BibTeX/natbib:
references/40-bibtex-natbib.md - Labels/cross-references:
references/41-cross-referencing.md - Reviewer report:
references/50-review-report.md - Response to reviewers:
references/51-response-to-reviewers.md - Research proposal/project cycle:
references/70-project-proposal.md - Book manuscript workflow:
references/71-book-manuscript.md - Tooling/reproducibility:
references/80-tooling.md
Built-in assets
- Response letter (LaTeX):
assets/response-letter-template.tex - Reviewer report (Markdown):
assets/reviewer-report-template.md - Reviewer report (LaTeX):
assets/reviewer-report-template.tex - Generic section skeleton:
assets/section-skeleton.tex - Manuscript starter (LaTeX):
assets/manuscript-template.tex - Book manuscript starter (LaTeX):
assets/book-manuscript-template.tex
Optional scripts (deterministic checks)
- Manuscript checks:
python scripts/check_tex.py path/to/main.tex - Citation/BibTeX checks:
python scripts/check_bib.py --tex path/to/main.tex --bib path/to/refs.bib - Combined run:
python scripts/audit_paper.py --tex path/to/main.tex --bib path/to/refs.bib
These checks are heuristic and do not compile LaTeX.
Workflows
Workflow A - Finished paper to abstract + keywords
- Read introduction/methods/results/discussion.
- Use
references/11-abstract.mdandreferences/12-keywords.md. - Draft abstract (default 6-8 sentences, acceptable 4-10, no citations, no math notation).
- Draft 6-10 keywords, alphabetized, avoid repeating title terms.
- Return:
egin{abstract}...nd{abstract}\keywords{...}(or venue-specific command)- short compliance checklist.
Workflow B - Manuscript audit
- Run
check_tex.py(andcheck_bib.pyif.bibexists). - Use
references/31-general-style.md,references/40-bibtex-natbib.md, and section-specific references. - Return top issues ranked by severity and concrete LaTeX edits.
- For JDS profile, explicitly call out line numbers, vector graphics, cleaned BibTeX, and reproducibility supplement readiness.
Workflow C - Reviewer report drafting
- Use
references/50-review-report.md. - Write summary + overall assessment + numbered major/minor comments.
- Keep tone constructive and professional.
- If requested, output using
assets/reviewer-report-template.tex.
Workflow D - Response to reviewers
- Use
references/51-response-to-reviewers.md. - Structure by Editor, Associate Editor, Reviewer sections.
- For every comment: quote, respond, quote manuscript change, add location.
- If requested, render with
assets/response-letter-template.tex.
Workflow E - Outline to full section
- Identify section type.
- Use
references/60-outline-to-section.md+ relevant section reference. - Expand bullets into coherent paragraphs with transitions.
- Use placeholders where information is missing.
Workflow F - Book manuscript scaffolding
- Use
references/71-book-manuscript.md. - Start from
assets/book-manuscript-template.tex. - Build frontmatter/mainmatter/backmatter and chapter map.
- Keep notation generic by default; add optional custom notation block only when requested.
Copy/paste prompt patterns
Abstract + keywords
"Use stat-writing. Read main.tex and draft a compliant abstract (default 6-8 sentences, acceptable 4-10; no citations; no math notation) and 6-10 alphabetical keywords. Output LaTeX blocks."
Full audit
"Use stat-writing. Audit main.tex (+ refs.bib). Run scripts if allowed. Return top issues with HIGH/MED/LOW and patch-ready LaTeX fixes."
Response to reviewers
"Use stat-writing. Here are reviewer/editor comments. Write a point-by-point response letter with quoted manuscript revisions and locations."
Reviewer report
"Use stat-writing. Draft a reviewer report with summary, overall assessment, numbered major comments, and numbered minor comments."
Book manuscript
"Use stat-writing. Start a book manuscript from chapter bullets using the book template. Produce frontmatter/mainmatter/backmatter and chapter-by-chapter drafting plan."