AgentSkillsCN

writing-assistant

在上下文感知的基础上，对文字进行改写、修正与拓展，助力提升文本质量。适用于以下场景：(1) 帮助用户对文本进行改写，以提升清晰度、调整语气或优化风格；(2) 修正语法错误、拼写错误或标点失误；(3) 将粗略的想法、要点或片段扩展为完整的段落与篇章。触发短语包括“改写这段文字”、“修正这段文本”、“帮我写作”、“拓展这个想法”，或仅需提供一段有待润色的文字即可。

SKILL.md
--- frontmatter
name: writing-assistant
description: >
  Rephrase, correct, and expand writing with context-aware improvements.
  Use when the user needs help with (1) Rephrasing text for clarity, tone,
  or style improvements, (2) Correcting grammatical errors, typos, or spelling
  mistakes, (3) Expanding rough ideas, bullet points, or fragments into full prose.
  Trigger phrases include "rephrase this", "fix this text", "help me write",
  "expand this idea", or simply providing text that needs improvement.

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 CharacteristicsModeAction
Mostly correct but could be clearer/betterRephraseImprove clarity, tone, style
Obvious errors (grammar, typos, spelling)CorrectionFix errors, minimal changes
Fragments, bullets, rough ideasIdea ExpansionDevelop 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