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/22-methods.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 的集中参考。如有侵权,请联系删除。
-->
# Methods section guidance
## Goal
A strong Methods section lets a reader understand **what is being estimated**, **under what assumptions**, **how it is estimated**, and **how uncertainty is quantified**.
## Principle: intuition before notation
Start with a plain-language overview (what the method does, what problem it solves) before introducing full notation.
## Minimum elements checklist
1. **Problem setup & estimand**
- Define the target quantity (estimand) in words.
2. **Assumptions**
- State modeling or identification assumptions explicitly.
3. **Notation**
- Define symbols once, keep consistent.
4. **Model / procedure**
- Specify the model or algorithm steps.
5. **Inference / uncertainty**
- Standard errors, confidence intervals, tests, or posterior summaries.
6. **Tuning / implementation details**
- Only what is necessary to reproduce.
## Suggested paragraph outline
1. High-level method summary.
2. Notation and data structure.
3. Model/estimand.
4. Estimation procedure.
5. Uncertainty + inference.
6. Practical notes (computation, hyperparameters, diagnostics).
## Writing tips
- Keep each paragraph focused on one idea.
- If you introduce new notation, define it immediately.
- If you compare to existing methods, explicitly state what differs.
## Output format tips (LaTeX)
- Use `\subsection{Method}` etc.
- Put long derivations in an appendix.
## Placeholders
- ` odo{define estimand}`
- ` odo{state assumptions}`
- ` odo{add algorithm pseudo-code}`
Never invent theoretical guarantees.
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 |