brycewang-stanford/Auto-Empirical-Research-Skills / skills/06-fuhaoda-stats-paper-writing/stat-writing
stat-writing
UnverifiedEnd-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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| references/10-title.md | markdown | 2.8 KB |
| references/11-abstract.md | markdown | 2.9 KB |
| references/12-keywords.md | markdown | 2.0 KB |
| references/20-introduction.md | markdown | 2.7 KB |
| references/21-data.md | markdown | 2.2 KB |
| references/22-methods.md | markdown | 2.4 KB |
| references/23-simulation.md | markdown | 2.6 KB |
| references/24-application.md | markdown | 2.0 KB |
| references/25-discussion.md | markdown | 1.9 KB |
| references/30-other-sections.md | markdown | 2.0 KB |
| references/31-general-style.md | markdown | 2.2 KB |
| references/32-english.md | markdown | 1.8 KB |
| references/40-bibtex-natbib.md | markdown | 2.1 KB |
| references/41-cross-referencing.md | markdown | 1.7 KB |
| references/50-review-report.md | markdown | 2.7 KB |
| references/51-response-to-reviewers.md | markdown | 2.4 KB |
| references/60-outline-to-section.md | markdown | 2.5 KB |
| references/70-project-proposal.md | markdown | 1.7 KB |
| references/71-book-manuscript.md | markdown | 2.4 KB |
| references/80-tooling.md | markdown | 2.0 KB |
references/10-title.md
View on GitHub<!--
╔══════════════════════════════════════════════════════════════╗
║ 本文件为开源 Skill 原始文档,收录仅供学习与研究参考 ║
║ CoPaper.AI 收集整理 | https://copaper.ai ║
╚══════════════════════════════════════════════════════════════╝
来源仓库: https://github.com/fuhaoda/stats-paper-writing-agent-skills
项目名称: stats-paper-writing-agent-skills
开源协议: MIT License
收录日期: 2026-04-02
声明: 本文件版权归原作者所有。此处收录旨在为社会科学实证研究者
提供 AI Agent Skills 的集中参考。如有侵权,请联系删除。
-->
# Title guidance (statistical papers)
## What a good title should do
A strong title should:
- **Predict the paper’s content** (so the right readers click and keep reading).
- **Attract the reader** (without hype).
- **Signal the tone** (methods paper vs application paper).
- **Contain the key search terms** your audience will use.
## Practical rules
- **Write the title late**: after you know the real contribution.
- Prefer **key phrases** over full sentences.
- Keep it **short and specific** (avoid filler like “A study of …”).
- Avoid unexplained abbreviations.
- Put the **most informative words early**.
- Avoid mathematical symbols in the title unless required by the venue.
## Common title patterns
Pick one pattern and fill in the blanks.
### Pattern A — Method + task + setting
> *[Method]* for *[Task]* in *[Setting/Data]*
Example skeleton:
- “Bayesian … for … in …”
- “Regularized … for … with …”
### Pattern B — Problem framing
> *[Task/Problem]* under *[Constraint]*
Example skeleton:
- “Inference for … under …”
- “Prediction with … under …”
### Pattern C — Contribution statement (careful: don’t overclaim)
> *A [new/adaptive/robust] [method/model] for [task]*
Avoid words like “first”/“unique” unless you can defend them.
### Pattern D — Application first (for applied journals)
> *[Domain/Outcome]*: *[Statistical method]*
## Quick checklist
- Does the title clearly indicate:
- the **problem/task**?
- the **method/model family**?
- the **application or data setting** (if relevant)?
- Would someone searching for the method/domain find this paper?
- Is it free of empty phrases (“novel”, “new”, “powerful”)?
## Output format tips (LaTeX)
Return a ready-to-paste line:
```tex
itle{...}
```
If you propose multiple options, provide 3–7 candidates and briefly explain the tradeoffs (precision vs breadth, methods vs application emphasis).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |