Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cfe Style

ASecurity

Use when polishing the language and rhetoric of a 《财经研究》 manuscript — eliminating empty-significance phrases, fixing vague policy talk, replacing method-flexing with mechanism, and aligning tense / person / hedging with CSSCI house style.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agents

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill cfe-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cfe Style?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Cfe Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-cfe-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-cfe-style)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: cfe-style
description: Use when polishing the language and rhetoric of a 《财经研究》 manuscript — eliminating empty-significance phrases, fixing vague policy talk, replacing method-flexing with mechanism, and aligning tense / person / hedging with CSSCI house style.
---

# 语言风格(cfe-style)

## 触发时机

- 通读初稿后觉得"读起来像政策文件 / 工作汇报"
- 一段里出现 ≥ 2 个"具有重要意义" / "为...提供新视角"
- 政策建议读起来像"加强、完善、推进"三件套
- 自检发现"经济含义未阐述" / "表格只报数字不解读"

## 对照表(黑名单 → 白名单)

| 问题类型 | 黑名单(删/改)                       | 白名单(替换为)                                        |
|----------|-----------------------------------|---------------------------------------------------|
| 空洞价值 | "具有重要的理论价值"               | "为理解 X 提供了 Y 视角下的分析框架"               |
| 空洞意义 | "对 XX 具有重要的参考价值"         | "本文结果意味着 XX 政策的传导渠道应纳入 YY"      |
| 泛泛建议 | "应加强监管 / 完善制度 / 推进改革" | "本文结果提示在 X 环节关注 Z 类企业的 Y 风险"     |
| 方法炫耀 | "本文使用复杂的 DML 模型"         | "本文采用双重机器学习处理高维控制变量内生选择"     |
| 贡献模糊 | "丰富了现有研究"                   | "首次利用交错 DID 识别策略考察了 X 对 Y 的影响"   |
| 文献堆砌 | "(张三,2020;李四,2021;...)"  | 按贡献分述:理论文献一段、实证文献一段、本文位置一段 |
| 表格无解读 | "表 3 报告了基准回归结果。"       | "表 3 显示,X 上升 1 个标准差使 Y 提高 0.04 个标准差,约相当于均值的 X%" |
| 数据来源含糊 | "数据来源于公开渠道"            | "数据来自国泰安数据库与全国税收调查匹配样本"     |
| 套话型贡献 | "为 XX 提供新的视角"               | "区别于 XXX(202X)使用的 OLS,本文……"           |

## 行文规范

### 时态

- 描述本文方法 / 数据 → **现在时**:本文使用 / 本文构建
- 报告实证结果 → **过去时**:研究发现 / 本文检验了
- 解释结果的经济含义 → **现在时**:这意味着 / 这一发现表明

### 人称

- 避免"笔者""我们认为"出现在结论性段落
- 可用:"本文发现 / 研究表明 / 结果显示"
- 英文版避免 "We feel that..." / "It is believed that..."

### 谦逊与边界

- 不要写"本文证明了"——经验研究只能说"本文提供了证据支持"
- 不要把统计显著当作经济显著——同时报告**经济量级**

## 一段一概括

每个段落第一句必须是**概括句**,后续句子是支撑。审稿人快速读完每段首句应能复原文章逻辑。

错误:
> 张三(2020)研究发现……。李四(2021)发现……。王五(2022)发现……。

正确:
> 既有研究就减税对企业投资的影响达成了两种对立判断(张三,2020;李四,2021)。一类研究认为……,另一类研究认为……。两种判断的分歧在于……。

## 行文自检清单

- [ ] 每段首句是概括性陈述
- [ ] 黑名单短语命中数 = 0
- [ ] 政策含义回扣中国现实、不空喊"加强重视"
- [ ] 表格后有经济含义解读,不仅报数字
- [ ] 数据来源点名到数据库
- [ ] 时态、人称在全文统一
- [ ] 显著性与经济量级同时报告

## 反模式

- 通篇"具有重要的 X 意义" —— 一次都不应出现
- 政策建议用"加强、完善、推进、深化"四个动词撑满段落
- 方法描述长于结果阐释
- 引言里塞 5 个并列文献 [27,28,29,30,31] —— 拆开分述
- 数据来源写"公开渠道"

## 输出格式

```
【黑名单命中】X 处,分别在:[...]
【段首概括率】X / 总段数
【数据来源点名】到位 / 待补
【经济含义阐述】到位 / 缺失 [...]
【时态/人称一致性】一致 / 待统一
【下一步】cfe-submission
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

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', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →