Academic Poster Builder
wanshuiyin/Auto-claude-code-research-in-sleep
Builds an academic conference poster as a single HTML and CSS file with measurement-based gates, real paper figures and a print-ready PDF rendered through headless Chromium.
经济金融论文写作编排器。根据PAPEROUTLINE.md和REFINEDDESIGN.md，编排调用fin-paper-draft（正文写作）、fin-paper-figure（图表生成）、fin-review-loop（review循环），管理版本并确保章节间的一致性。
Install Fin Paper Writing
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install csmar432/finai-research fin-paper-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fin-paper-writing .claude/skills/fin-paper-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .claude/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install csmar432/finai-research fin-paper-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fin-paper-writing .agents/skills/fin-paper-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .agents/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install csmar432/finai-research fin-paper-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fin-paper-writing .cursor/skills/fin-paper-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .cursor/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/csmar432/finai-research.git --path .agents/skills/fin-paper-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install csmar432/finai-research fin-paper-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fin-paper-writing .gemini/skills/fin-paper-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .gemini/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install csmar432/finai-research fin-paper-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fin-paper-writing .github/skills/fin-paper-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .github/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add csmar432/finai-research --skill fin-paper-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install csmar432/finai-research fin-paper-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/csmar432/finai-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fin-paper-writing .opencode/skills/fin-paper-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fin-paper-writing" agent skill from https://github.com/csmar432/finai-research/tree/main/.agents/skills/fin-paper-writing into .opencode/skills/fin-paper-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fin-paper-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fin-paper-writing- GitHub stars
- 109
- Token cost
- ~2.3k tokens
- SKILL.md length
- 345 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- MIT
At a glance
经济金融论文写作编排器。根据PAPEROUTLINE.md和REFINEDDESIGN.md，编排调用fin-paper-draft（正文写作）、fin-paper-figure（图表生成）、fin-review-loop（review循环），管理版本并确保章节间的一致性。
- Works in 10 steps: 方法论先写。先写methodology和results，有助于理清思路，避免int… → 章节独立追踪。每个章节有自己的状态、字数、最后修改时间。 → 一致性是底线。图表编号、表编号、公式编号必须在正文和计划文件中完全一致。 → …
- Tasks that involve Scientific writing
- SKILL.md covers 触发条件, 与 fin-full-pipeline 的关系, 前置条件检查 and 章节写作顺序（关键原则）, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Fin Paper Writing is an agent skill from csmar432/finai-research. 经济金融论文写作编排器。根据PAPEROUTLINE.md和REFINEDDESIGN.md，编排调用fin-paper-draft（正文写作）、fin-paper-figure（图表生成）、fin-review-loop（review循环），管理版本并确保章节间的一致性。
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Scientific writing, Design tokens and Econometrics and empirical research. It works with LaTeX. The repository describes itself as: Evidence-first AI workflow for economic and financial research: literature → identification → data → econometrics → verifiable LaTeX. 43 data sources, 58 method modules, 18 AI… The licence is MIT.
When your agent uses it
- Tasks that involve Scientific writing
- Tasks that involve Design tokens
- Tasks that involve Econometrics and empirical research
Example prompts
- “/fin-paper-writing”
Requirements
- Python 3
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- 方法论先写。先写methodology和results，有助于理清思路，避免intro空洞。
- 章节独立追踪。每个章节有自己的状态、字数、最后修改时间。
- 一致性是底线。图表编号、表编号、公式编号必须在正文和计划文件中完全一致。
- Review在整合后。等图表和正文都写完再做Review，避免重复Review。
- 版本是审计记录。每次重大修改都要记录变更原因和审查意见采纳情况。
- 中文论文写作顺序略有不同。中文期刊常按顺序写（引言→文献→方法→结果→结论）。
- 写作过程要记录。在VERSION_MANIFEST.md中实时更新状态。
- 终稿前必须通过submit-check。格式和匿名性是编辑初审的门槛。
- 占位符规则。首次生成用[coef]、[se]、[N]占位，由数据填充。
- 每次保存后自动更新状态。章节完成、修改、保存后立即更新CHAPTER_STATUS.md。
What it can do on your machine
Read from SKILL.md and the folder at commit 47eebb7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fin Paper Writing loads about 2.3k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 345 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from csmar432/finai-research at commit 47eebb7, republished under its MIT licence (© csmar432). 345 words, ~2,332 tokens.
Download SKILL.mdSave it as
.claude/skills/fin-paper-writing/SKILL.md (or your agent's skills folder).- name
- fin-paper-writing
- description
- 经济金融论文写作编排器。根据PAPER_OUTLINE.md和REFINED_DESIGN.md，编排调用fin-paper-draft（正文写作）、fin-paper-figure（图表生成）、fin-review-loop（review循环），管理版本并确保章节间的一致性。
- argument-hint
- outline-reference
经济金融论文写作编排器
编排从大纲到可投稿论文的全流程，管理章节间的引用一致性和版本迭代。
触发条件
触发关键词：写论文、paper writing、论文写作、开始写作
与 fin-full-pipeline 的关系
fin-full-pipeline 负责"研究"阶段（lit→idea→novelty→design），
本技能负责"写作"阶段（outline→draft→figure→review→convert）。
fin-full-pipeline 终点
↓ PAPER_OUTLINE.md + REFINED_DESIGN.md
fin-paper-writing（写作编排）
↓
┌──────────────────────────────────────────┐
│ 阶段A: 正文写作 (fin-paper-draft) │
│ → 生成 draft_v{N}/introduction.tex │
│ ↓ checkpoint │
│ 阶段B: 图表生成 (fin-paper-figure) │
│ → 生成 draft_v{N}/figures/*.pdf │
│ ↓ checkpoint │
│ 阶段C: 整合检查（章节一致性） │
│ → 验证引用、表编号、图编号 │
│ ↓ checkpoint │
│ 阶段D: 对抗性Review (fin-review-loop) │
│ → 多轮review直到达标 │
│ ↓ checkpoint │
│ 阶段E: 编译 (fin-paper-convert) │
│ → 生成 main.pdf │
│ ↓ │
│ 阶段F: 投稿前检查 (fin-submit-check) │
│ → SUBMIT_CHECK_REPORT.md │
└──────────────────────────────────────────┘
↓
输出: draft_v{N}/main.pdf（可投稿）前置条件检查
Phase A: Pre-writing Checklist
在开始写作前，验证以下文件存在：
| 检查项 | 文件路径 | 说明 |
|---|---|---|
| [ ] 论文大纲 | output/fin-manuscript/PAPER_OUTLINE.md | 章节结构和内容要点 |
| [ ] 研究设计 | output/fin-refinement/REFINED_DESIGN.md | 变量定义、识别策略 |
| [ ] 实证结果 | output/fin-experiments/results/ | 表格/图表文件 |
| [ ] 参考文献 | draft_v{N}/references.bib | BibTeX格式 |
| [ ] 研究简报 | FIN_BRIEF.md | 目标期刊、语言 |
如果任何文件缺失，停止并提示用户先完成前置步骤。
章节写作顺序（关键原则）
Phase B: Chapter Writing Order
始终使用此顺序，不要按论文的自然顺序写：
推荐顺序（而非论文顺序）：
1. Data & Methodology → 先写方法，数据最清晰
2. Descriptive Statistics → 紧跟方法
3. Main Results → 结果最清晰，容易写
4. Mechanism Analysis → 如果有
5. Heterogeneity Analysis → 如果有
6. Robustness Checks → 紧凑汇总
7. Conclusion → 有全篇在手，总结更全面（最难）
8. Introduction → 最后写intro，知道全貌，贡献更清晰
9. Literature Review & Hypotheses → H1/H2/H3框架
10. Abstract → 写完所有章节后，自然形成摘要为什么这样排序？
- 方法和数据是基础，写完就清楚论文的"做什么"
- 结果是论文核心，先写建立信心
- 结论需要全篇在手，最后写才能全面总结
- 引言需要知道结论，才能准确描述贡献
- 摘要需要知道全文，才能精炼概括
编排协调
Phase C: Orchestration
编排调用以下子技能：
# 协调关系图：
fin-paper-writing (编排器)
│
├──→ fin-paper-draft (正文写作)
│ 每个章节独立生成
│
├──→ fin-paper-figure (图表生成)
│ 图表生成后与正文交叉引用
│
├──→ fin-ref-paper (参考文献管理)
│ 确保引用格式一致
│
└──→ fin-review-loop (Review循环)
每章节完成后Review调用方式（Cursor Skill语法）：
<!-- 写方法论章节 -->
Skill: fin-paper-draft
"methodology"
<!-- 生成图表 -->
Skill: fin-paper-figure
"main_results"
<!-- 管理参考文献 -->
Skill: fin-ref-paper
"update"
<!-- Review章节 -->
Skill: fin-review-loop
"methodology_v1"版本管理
Phase D: Version Management
VERSION_MANIFEST.md
维护版本变更记录：
# 版本清单
**论文标题**: [标题]
**目标期刊**: [期刊]
**当前版本**: draft_v{N}
## 版本历史
| 版本 | 日期 | 主要变更 | 作者 |
|------|------|---------|------|
| draft_v1 | 2026-06-13 | 初始草稿 | Agent |
| draft_v2 | 2026-06-14 | 补充机制检验 | Agent |
| draft_v3 | 2026-06-15 | 根据Review修改引言 | Human |
## 当前状态
| 章节 | 状态 | 字数 | 最后修改 |
|------|------|------|---------|
| introduction.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 1,234 | 2026-06-13 |
| literature.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 2,345 | 2026-06-13 |
| methodology.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 1,567 | 2026-06-12 |
| results.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 3,210 | 2026-06-12 |
| robustness.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 890 | 2026-06-13 |
| conclusion.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 678 | 2026-06-13 |
| abstract.tex | [DRAFT/REVIEWING/REVISED/FINAL] | 250 | 2026-06-13 |
| references.bib | [DRAFT/REVIEWING/REVISED/FINAL] | — | 2026-06-13 |CHAPTER_STATUS.md
追踪每个章节的详细状态：
# 章节状态追踪
## 章节详情
### introduction.tex
- **状态**: DRAFT
- **字数**: 1,234
- **创建时间**: 2026-06-13 10:00
- **最后修改**: 2026-06-13 14:30
- **Review轮次**: 0
- **检查清单**:
- [x] 动机充分
- [x] 3个贡献点清晰
- [ ] 字数符合期刊要求
- [x] Roadmap包含
- **备注**: 需补充第3个贡献点
### methodology.tex
- **状态**: REVIEWING
- **字数**: 1,567
- **Review轮次**: 1
- **Review反馈**: 通过版本迭代流程
当需要重大修改时：
## 创建新版本流程
1. 将 draft_v{N}/ 复制为 draft_v{N+1}/
2. 在 VERSION_MANIFEST.md 中记录：
| draft_v{N+1} | [日期] | [修改原因] | Agent/User |
3. 在 CHAPTER_STATUS.md 中标记需修改的章节为"重写"
4. 执行修改
5. 重新执行 阶段C（一致性检查）→ 阶段D（Review）→ 阶段E（编译）→ 阶段F（检查）一致性检查
Phase E: Consistency Checks
每章节完成后，自动执行以下检查：
检查1：图表编号一致性
| 图编号 | FIGURE_PLAN中的位置 | 正文引用 | 状态 |
|---|---|---|---|
| fig1_sample | 3.1（样本构建） | \ref{fig1_sample} in §3.1 | ✅/❌ |
| fig2_trend | 3.2（描述统计） | \ref{fig2_trend} in §3.2 | ✅/❌ |
| fig3_main | 4.1（主结果） | \ref{fig3_main} in §4.1 | ✅/❌ |
| fig4_hetero | 4.3（异质性） | \ref{fig4_hetero} in §4.3 | ✅/❌ |
| fig5_mechanism | 4.4（机制） | \ref{fig5_mechanism} in §4.4 | ✅/❌ |
| fig6_placebo | 4.5（稳健性） | \ref{fig6_placebo} in §4.5 | ✅/❌ |
检查2：表格编号一致性
| 表编号 | TABLE_PLAN中的位置 | 正文引用 | 状态 |
|---|---|---|---|
| tab:var_def | 3.2（变量定义） | \ref{tab:var_def} | ✅/❌ |
| tab:summary | 3.3（描述性统计） | \ref{tab:summary} | ✅/❌ |
| tab:main | 4.1（主回归） | \ref{tab:main} | ✅/❌ |
| tab:heterogeneity | 4.3（异质性） | \ref{tab:heterogeneity} | ✅/❌ |
| tab:robustness | 4.5（稳健性） | \ref{tab:robustness} | ✅/❌ |
检查3：假设与结果一致性
| 假设 | 章节位置 | 结果位置 | 对应结论 | 状态 |
|---|---|---|---|---|
| H1 | §2.3 | §4.1 | [结论] | ✅/❌ |
| H2 | §2.3 | §4.3 | [结论] | ✅/❌ |
| H3 | §2.3 | §4.4 | [结论] | ✅/❌ |
检查4：引用一致性
- 所有
\cite{}都在references.bib中存在 - 引用格式统一（JF风格/GB-T-7714）
- 无"幽灵引用"（引用但无对应条目）
检查5：文字质量检查（新增）
每章节完成后，必须执行以下 AI 味和底气检测：
AI 味检测清单（扫描到任一关键词即为不合格）：
扫描关键词（中文）：值得注意的是 | 综上所述 | 从某种意义上 | 客观来说 | 在一定程度上 | 某种程度上 | 相对而言 | 近年来 | 随着时代发展 | 当今社会 | 可能存在 | 有待进一步研究 | 首先我们需要 | 非常重要的 | 具有重大意义的 | 已经被 | 可以被认为 | XX研究表明
底气指数评估（结论段必须满足≥1项）：
| 底气要素 | 检测标准 |
|---|---|
| 具体数字 | β = X.XXX，95% CI [...]，p = X |
| 经济规模 | 占均值/标准差的 X% |
| 机制描述 | 通过 X 渠道，而非 Y 渠道 |
| 对比发现 | A 效应是 B 效应的 X 倍 |
| 理论对应 | 与 [理论名] 的预测一致/相反 |
表格引导句检查：每张表格前是否有≥2句引导（主题句 + 来源句 + 核心发现句），每张表格后是否有≥1句解读。
图表注释解读检查：每个图表的 caption/注释是否包含"说明什么"（而不仅是"展示什么"），是否包含具体数字或对比描述。
语言质量检查不通过的章节，不得进入 Review 环节，必须先重写。
语言质量标准（新增）
T07：语言质量 Review 环节
在 Phase C（Orchestration）中，每章节写作完成后，必须触发语言质量 Review：
<!-- 每章节完成后执行 -->
Skill: fin-paper-draft
"language_check"语言质量 Review 标准：
| 检查项 | 标准 | 不通过处置 |
|---|---|---|
| AI 味关键词 | 全文出现 ≤ 0 次 | 重写对应段落 |
| 底气指数 | 结论段满足 ≥ 1 项 | 重写结论段 |
| 表格引导句 | 每表前后 ≥ 3 句 | 补充引导句 |
| 图表注释 | 每图 ≥ 1 句解读 | 补充注释 |
| 段落数 | 符合 PAPER_OUTLINE.md 下限 | 扩充或合并 |
T08：CHAPTER_STATUS.md 语言质量字段
更新 CHAPTER_STATUS.md 模板，增加语言质量追踪字段：
### introduction.tex
- **状态**: DRAFT
- **字数**: 1,234
- **语言质量检查**:
- [ ] AI 味关键词: 0次（要求 ≤ 0）
- [ ] 底气指数: 结论段含具体数字（是/否）
- [ ] 表格引导句: 每表前后 ≥ 3句（是/否）
- [ ] 图表注释: 每图 ≥ 1句解读（是/否）VERSION_MANIFEST.md 新增语言质量维度
版本记录中新增语言质量维度：
| 版本 | 日期 | 主要变更 | 语言质量 | 作者 |
|------|------|---------|---------|------|
| draft_v1 | 2026-06-13 | 初始草稿 | AI味0/底气足 | Agent |输出文件结构
output/fin-manuscript/draft_v{N}/
├── introduction.tex # 引言
├── literature.tex # 文献综述与假说
├── methodology.tex # 数据与实证方法
├── results.tex # 实证结果
├── robustness.tex # 稳健性检验
├── conclusion.tex # 结论
├── abstract.tex # 摘要
├── references.bib # 参考文献
├── tables/ # 表格文件
│ ├── tab1_var_def.tex
│ ├── tab2_summary.tex
│ └── ...
├── figures/ # 图表文件
│ ├── fig1_sample.pdf
│ ├── fig2_trend.pdf
│ └── ...
├── VERSION_MANIFEST.md # 版本清单
├── CHAPTER_STATUS.md # 章节状态
├── CONSISTENCY_CHECK.md # 一致性检查报告
└── main.pdf # 编译后的PDFCheckpoint（检查点）
每个Phase完成后必须暂停，等待用户确认：
| 检查点 | 内容 | 用户操作 |
|---|---|---|
| Phase A完成 | 所有前置文件验证 | 确认开始写作 |
| 每章节完成 | 章节草稿生成 | Review通过后继续 |
| Phase C完成 | 一致性检查报告 | 确认无问题 |
| Phase D完成 | Review通过报告 | 确认进入编译 |
| Phase E完成 | PDF编译成功 | 确认格式 |
| Phase F完成 | 投稿检查报告 | 确认提交 |
Review重点（按章节）
| 章节 | Review重点 |
|---|---|
| introduction | 动机是否充分？贡献是否夸大？字数是否合规？ |
| literature | 文献覆盖是否完整？假设推导是否有理论支撑？ |
| methodology | 识别策略是否合理？数据处理是否透明？ |
| results | 表格解读是否准确？经济意义讨论是否充分？ |
| conclusion | 是否过度推断？局限性是否诚实？ |
控制标志
| 标志 | 默认值 | 说明 |
|---|---|---|
| STRICT_MODE | true | 每章写完后必须通过检查清单才能继续 |
| REVIEW_ROUNDS | 4 | 最大review轮次 |
| AUTO_COMPILE | false | 每次章节修改后是否自动编译 |
| VERSION_CONTROL | true | 重大修改是否自动创建新版本 |
| CHECKPOINT_ENABLED | true | 每个Phase后是否暂停等待确认 |
关键原则
- 方法论先写。先写methodology和results，有助于理清思路，避免intro空洞。
- 章节独立追踪。每个章节有自己的状态、字数、最后修改时间。
- 一致性是底线。图表编号、表编号、公式编号必须在正文和计划文件中完全一致。
- Review在整合后。等图表和正文都写完再做Review，避免重复Review。
- 版本是审计记录。每次重大修改都要记录变更原因和审查意见采纳情况。
- 中文论文写作顺序略有不同。中文期刊常按顺序写（引言→文献→方法→结果→结论）。
- 写作过程要记录。在VERSION_MANIFEST.md中实时更新状态。
- 终稿前必须通过submit-check。格式和匿名性是编辑初审的门槛。
- 占位符规则。首次生成用
[coef]、[se]、[N]占位，由数据填充。 - 每次保存后自动更新状态。章节完成、修改、保存后立即更新CHAPTER_STATUS.md。
© csmar432, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/fin-paper-writing of csmar432/finai-research.
Open the folder on GitHubat commit 47eebb7
Compare with similar skills
Fin Paper Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fin Paper Writing this skillcsmar432/finai-research | 109 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Academic Poster Builderwanshuiyin/Auto-claude-code-research-in-sleep | 17k | 1 repos | ~4.5k | Automated safety check: Notes | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Econ Writehanlulong/econ-writing-skill | 651 | 2 repos | ~14k | Automated safety check: Pass | MIT | |
| NSFC Grant Rationale Writerhuangwb8/ChineseResearchLaTeX | 2.9k | — | ~945 | Automated safety check: Pass | MIT | |
| Collaborating With Claudeappautomaton/latex-arxiv-SKILL | 458 | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Econ Write
hanlulong/econ-writing-skill
Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists.
NSFC Grant Rationale Writer
huangwb8/ChineseResearchLaTeX
Writes, restructures, reviews and polishes the rationale section of NSFC research grant applications in LaTeX, with backups and a diff before every write.
Collaborating With Claude
appautomaton/latex-arxiv-SKILL
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review.
Journal Selector for Manuscripts
huangwb8/ChineseResearchLaTeX
Recommends journals for a manuscript by filtering a bundled impact-factor catalog, verifying scope and quality online, and writing a ranked Markdown report.
More from csmar432/finai-research
All 15 skills in this repoFin Arch Diagram
csmar432/finai-research
生成研究/项目架构图、流程图、层次图（swimlane / processflow / hierarchytree）。适合 PPT 汇报、技术文档、综述插图。输出风格接近 draw.io，可选 graphviz（高质量）/ matplotlib（零依赖）双后端。
Fin Brief Generator
csmar432/finai-research
根据用户输入或已有研究输出（文献综述/想法报告/新颖性报告），自动生成或更新FINBRIEF.md，减少用户填写负担. An agent skill from csmar432/finai-research.
Fin Data Acquisition
csmar432/finai-research
根据REFINEDDESIGN.md中的变量定义，自动获取所需数据并生成可执行的回归分析脚本（Python/Stata）。
Fin Experiment Design
csmar432/finai-research
经济金融实证方法设计。根据研究想法和REFINEDDESIGN.md，生成完整的实证研究设计方案，覆盖识别策略选择、样本构建、变量定义、稳健性检验清单和内生性处理方案。
Fin Generate Idea
csmar432/finai-research
针对经济金融研究方向的创意生成与评估。生成8-12个可发表的研究idea，过滤后在数据可行的情况下进行小规模实证验证，输出排序后的研究想法报告。
Fin Idea Discovery
csmar432/finai-research
经济金融研究的完整想法发现流程。从研究方向出发，经过文献综述、想法生成、新颖性验证、实证方法设计和数据获取，输出经过数据实证验证的可执行研究方案。
Related
Works with
Categories
Questions about Fin Paper Writing
What does Fin Paper Writing do?
经济金融论文写作编排器。根据PAPEROUTLINE.md和REFINEDDESIGN.md，编排调用fin-paper-draft（正文写作）、fin-paper-figure（图表生成）、fin-review-loop（review循环），管理版本并确保章节间的一致性。. Fin Paper Writing is an agent skill from csmar432/finai-research.
When should I use Fin Paper Writing?
Fin Paper Writing fits situations like: tasks that involve Scientific writing; tasks that involve Design tokens; tasks that involve Econometrics and empirical research.
How do I install Fin Paper Writing in Claude Code?
Run `npx skills add csmar432/finai-research --skill fin-paper-writing -a claude-code`. Or copy the skill folder (.agents/skills/fin-paper-writing in csmar432/finai-research) into .claude/skills/fin-paper-writing in your project. Claude Code loads it when a task matches its description.
How do I install Fin Paper Writing in Codex?
Run `npx skills add csmar432/finai-research --skill fin-paper-writing -a codex`. Or copy the skill folder (.agents/skills/fin-paper-writing in csmar432/finai-research) into .agents/skills/fin-paper-writing in your project. Codex loads it when a task matches its description.
Can I use Fin Paper Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add csmar432/finai-research --skill fin-paper-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fin-paper-writing, .gemini/skills/fin-paper-writing, .github/skills/fin-paper-writing and .opencode/skills/fin-paper-writing in your project.
What does Fin Paper Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Fin Paper Writing is instructions for the agent only. Our summary lists: Python 3.
Does Fin Paper Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Fin Paper Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fin Paper Writing use?
Fin Paper Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fin Paper Writing use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fin Paper Writing?
Skills that share tags, products or a category with Fin Paper Writing: Academic Poster Builder (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Econ Write (hanlulong/econ-writing-skill, 651 stars) and NSFC Grant Rationale Writer (huangwb8/ChineseResearchLaTeX, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fin Paper Writing?
csmar432 (a GitHub user) maintains it in csmar432/finai-research, which has 109 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 6, 2026.
Source: csmar432/finai-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.