返回 Skill 列表
extension
分类: 内容与媒体无需 API Key

writing-assistant

重新表述、纠正和扩展写作内容,根据上下文进行改进。当用户需要帮助时使用:(1)为了更清晰、调整语气或风格而重新表述文本;(2)纠正语法错误、打字错误或拼写错误;(3)将粗略的想法、要点或片段扩展为完整的散文。触发短语包括“重新表述这个”、“修正这段文字”、“帮我写”、“扩展这个想法”,或者直接提供需要改进的文本。

person作者: jakexiaohubgithub

Writing Assistant

Improve text through rephrasing, correction, or expansion based on user intent and context.

Modes

Determine which mode applies based on input analysis:

| Input Characteristics | Mode | Action | |----------------------|------|--------| | Mostly correct but could be clearer/better | Rephrase | Improve clarity, tone, style | | Obvious errors (grammar, typos, spelling) | Correction | Fix errors, minimal changes | | Fragments, bullets, rough ideas | Idea Expansion | Develop into full prose |

Workflow

1. Analyze Input

Identify the mode that best matches the input. If ambiguous, ask the user which approach they prefer.

2. Gather Context

Ask these questions before making changes:

For all modes:

  • Audience: casual, professional, technical, executive?
  • Tone: formal, friendly, assertive, neutral?
  • Length: concise or expanded?
  • Context: email, doc, slack, presentation?

Additional for Idea Expansion:

  • Main point to convey?
  • Specific details to include?
  • Desired reader action?

3. Present Result

Show revised text, then note what changed (2-3 bullets max). Ask if adjustments are needed.

Examples

Rephrase/Correction:

Input: "i think we shoud move the meeting to tuesday becuase john cant make it monday"

Questions:

  • Casual team chat or formal email?
  • Keep brief or add context?

Output (casual, brief): "Let's move the meeting to Tuesday - John isn't available Monday."

Changes:

  • Fixed spelling (should, because)
  • Made more direct
  • Kept casual tone

Idea Expansion:

Input: "idea: need to tell team about new deployment process, its complicated, people keep messing it up"

Questions:

  • What's the new process briefly?
  • What are people getting wrong?
  • Announcement, guide, or feedback request?

Output: [Full prose based on responses]

Constraints

  • Never change meaning or intent
  • Preserve technical terms and proper nouns exactly
  • Ask rather than assume when intent is unclear
  • Keep corrections minimal - avoid over-editing