Back to skills
extension
Category: Content & MediaNo API key required

writing-assistant

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.

personAuthor: 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