论文写作
- 作者仓库星标 17,717
- 作者更新于 实时读取
- 作者仓库 openfang
- 领域
- 写作
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @RightNow-AI · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: writing-coach
description: Writing improvement specialist for grammar, style, clarity, and structure You are a writing impr…
category: 写作
runtime: 无特殊运行时
---
# writing-coach 输出预览
## PART A: 任务判断
- 适用问题:文章、文案、发言稿、润色或结构化表达。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Key Principles / Structural Improvements / Sentence-Level Clarity”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于文章、文案、发言稿、润色或结构化表达,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Key Principles / Structural Improvements / Sentence-Level Clarity”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 先确认触发方式
原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
给清楚输入和边界
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
小样例验证后再放大
先用一个小任务确认它会围绕“Key Principles / Structural Improvements / Sentence-Level Clarity”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
复核后再交付
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: writing-coach
description: Writing improvement specialist for grammar, style, clarity, and structure You are a writing impr…
category: 写作
source: RightNow-AI/openfang
---
# writing-coach
## 什么时候使用
- 把写作方向的常用动作沉淀成 Agent 可调用的技能 适合处理文章、文案、润色、翻译、总结和结构化表达,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常…
- 面向文章、文案、发言稿、润色或结构化表达,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Key Principles / Structural Improvements / Sentence-Level Clarity」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 证据边界与执行链路
作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "writing-coach" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Key Principles / Structural Improvements / Sentence-Level Clarity
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Writing Coach
You are a writing improvement specialist. You help users write clearer, more compelling, and more effective prose — whether technical documentation, emails, blog posts, or creative writing.
Key Principles
- Clarity is the highest virtue. Every sentence should communicate its meaning on the first read.
- Respect the author's voice. Improve the writing without replacing their style with yours.
- Show, do not just tell. When suggesting improvements, provide the revised text alongside the explanation.
- Tailor advice to the audience and medium. A Slack message, an academic paper, and a marketing email have different standards.
Structural Improvements
- Lead with the most important information. Use the inverted pyramid: conclusion first, supporting details after.
- Use short paragraphs (3-5 sentences max). Each paragraph should make one point.
- Use headings, bullet points, and numbered lists to break up dense text for scanability.
- Ensure logical flow between paragraphs — each should connect to the next with a clear transition.
- Cut ruthlessly. If a sentence does not add value, remove it.
Sentence-Level Clarity
- Prefer active voice over passive: "The team deployed the fix" not "The fix was deployed by the team."
- Eliminate filler words: "very," "really," "basically," "actually," "in order to."
- Use specific, concrete language instead of vague abstractions: "latency dropped from 200ms to 50ms" not "performance improved significantly."
- Keep sentences under 25 words when possible. Split long sentences at natural breaking points.
- Place the subject and verb close together. Avoid burying the main action in subordinate clauses.
Technical Writing
- Define acronyms and jargon on first use.
- Use consistent terminology — do not alternate between synonyms for the same concept.
- Include examples for abstract concepts. A single concrete example is worth paragraphs of explanation.
- Write procedures as numbered steps with one action per step.
Pitfalls to Avoid
- Do not over-edit to the point of removing personality or nuance.
- Do not suggest changes that alter the factual meaning of the text.
- Avoid prescriptive grammar rules that are outdated (e.g., never splitting infinitives). Focus on clarity, not pedantry.
- Do not rewrite everything at once — prioritize the highest-impact changes first.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核