Use when running the final pre-submission preflight for 《经济研究》 — format, word count, double-blind, references, anti-plagiarism, author info, and supplementary files.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill er-submission --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Er Submission?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-er-submission)More formats (shields.io, HTML) on the badges page.
---
name: er-submission
description: Use when running the final pre-submission preflight for 《经济研究》 — format, word count, double-blind, references, anti-plagiarism, author info, and supplementary files.
---
# 投稿前 Preflight(er-submission)
## 触发时机
- "明天就要投了"
- 准备点提交按钮前的最后检查
- 不确定投稿系统需要哪些附件
## 投稿前 Checklist
### 格式
- [ ] 正文使用宋体小四 / 1.5 倍行距(具体看当年要求)
- [ ] 章节编号使用 一、二、三(一级)→(一)、(二)(二级)→ 1、2、3(三级)
- [ ] 图表编号连续且与正文引用对应
- [ ] 公式独立成行,居中,右侧带编号 (1) (2) ...
- [ ] 参考文献按文末统一格式:作者,年份,文章名,期刊,卷期,页码
### 字数
- [ ] 正文字数 1.5–2.5 万(含图表)
- [ ] 中文摘要 200–400 字
- [ ] 英文摘要 200–300 词
- [ ] 关键词中文 3–5 个 + 英文对应
- [ ] JEL Classification 至少 2 个
### 双盲
- [ ] 正文中**任何能识别作者身份**的内容已去除
- 自引使用"已有研究(XX,2020)",不要写"作者前期研究"
- 致谢页**单独**提交,不在正文中
- 项目基金信息**单独**提交
- 作者联系方式只在投稿系统中填,不写在正文
- [ ] 文件名不包含作者姓名 / 单位
### 参考文献
- [ ] 中文文献和英文文献按各自格式排列
- [ ] 中文期刊用全名(《经济研究》不写 EJR)
- [ ] 每条文献完整:作者、年份、题目、期刊 / 出版社、卷、期、页
- [ ] 文中出现的每条引用都在参考文献列表中
- [ ] 参考文献列表中的每条都在文中至少出现一次
- [ ] 理论文献是否齐全(《经济研究》易在此挑刺)
### 附件
- [ ] 致谢页(单独)
- [ ] 基金资助说明(单独)
- [ ] 作者简介(单独)
- [ ] 利益冲突声明(如有要求)
- [ ] 数据可用性声明(如有要求)
### 查重
- [ ] 知网查重 ≤ 15%(保险起见 ≤ 10%)
- [ ] 自引超过 5% → 单独说明
- [ ] 工作论文 / 会议论文版本是否已声明?
## 投稿系统操作要点
- 《经济研究》在线投稿系统:勤刷新,单次上传 ≤ 20MB
- 推荐审稿人 3 名(建议同领域、有相关发表、不与作者有合作)
- 不推荐审稿人 0–2 名
- 选择"研究类型"务必准确(实证 / 理论 / 综述 / 评论)
## 反模式
- 通宵改完没做双盲检查
- 参考文献仍是 EndNote 默认 APA 格式,未转为中文规范
- 图表编号断号 / 图 3 在正文中称"图 4"
- 投稿时把 working paper 版的致谢忘了删
- JEL Classification 缺失
## 输出格式
```
【字数】正文 X / 摘要 X
【双盲合规】通过 / 待修改:[...]
【参考文献条数】中文 X / 英文 Y
【JEL】已填 / 缺失
【查重率】X%
【附件齐全】是 / 否
【下一步】等待外审 / 收到 R&R → er-rebuttal
```
## 附属资源
- [`templates/manuscript_template.md`](templates/manuscript_template.md) — 标准稿件结构骨架(中英摘要、变量定义表、参考文献格式)
- [`templates/checklist.md`](templates/checklist.md) — 投稿前 8 类自检清单(格式 / 作者信息 / 摘要 / 结构 / 内容 / 图表 / 文献 / 系统)
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — 数据资源(CSMAR / Wind / CNRDS / CFPS / CHARLS 等)与统计软件包速查
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.