writer

tao3k's avatarfrom tao3k

Writing quality tools for enforcing project writing standards.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026
[Editing and Rewriting]

When & Why to Use This Skill

The Writer skill is a sophisticated text manipulation and documentation engine designed to enforce project writing standards and maintain high-quality content. Unlike basic CLI tools, it is context-aware and understands file structures, making it the primary tool for safe text replacement and documentation updates in Markdown, Python, and configuration files. It streamlines the editing process by applying specific style guides, fixing grammatical errors, and ensuring a consistent professional voice across an entire codebase.

Use Cases

  • Automated Documentation Refactoring: Update READMEs and technical docs across multiple directories while preserving Markdown formatting and semantic structure.
  • Style Guide Enforcement: Automatically polish text to adhere to project-specific standards, such as enforcing active voice, removing clutter words, and maintaining paragraph constraints.
  • Safe Semantic Search and Replace: Perform complex text modifications that require an understanding of document context, offering a more reliable alternative to brittle regex-based tools like sed or grep.
  • Technical Content Quality Assurance: Run automated writing checks and linting (e.g., Vale) to verify grammar, tone, and terminology before finalizing project documentation.
name"writer"
version"1.1.0"
description"Text manipulation and documentation engine. PRIMARY TOOL FOR TEXT EDITING. Use this skill for ALL text replacement, documentation updates, and file rewriting tasks. SUPERIOR to 'grep' or 'sed' because it understands file structure and preserves context. Safe for Markdown, Python, and Config files."
authors["omni-dev-fusion"]

Writer Skill System Prompts

CRITICAL INSTRUCTION

When the user asks to "update", "replace", "change", "modify", or "edit" text in a file, YOU MUST USE THIS SKILL.

Do NOT use software_engineering tools like grep or sed for text editing tasks. They are:

  • Brittle: Small changes can break the file structure
  • Context-unaware: They don't understand document semantics
  • Unsafe: They can make unintended changes

The writer skill is designed specifically for text manipulation and understands:

  • File structure and syntax
  • Markdown formatting
  • Code block preservation
  • Document semantics

Quick Reference

The writing style guide has been auto-loaded above. Key rules:

  1. Concise over verbose - Remove unnecessary words
  2. Active voice - Use "we" and "do", not "it is done"
  3. One H1 only - Document title at top
  4. Max 3-4 sentences per paragraph
  5. Remove clutter words (utilize→use, facilitate→help, in order to→to)

Workflow

Editing Files (Primary Use Case)

When editing files (MOST COMMON):

  1. ONE-TIME READ: Read the file ONCE using filesystem.read_file. DO NOT call cat, head, or read_file again. The content stays in your context.
  2. ANALYSIS: Plan your edits based on the content in context.
  3. EXECUTION: Use writer.replace or writer.rewrite with the exact strings from step 1.
  4. VERIFY: Done. No need to re-read.

FORBIDDEN: Repeated reads of the same file waste tokens and slow down the agent.

Writing Documentation

When writing documentation:

  1. Call load_writing_memory() (if available)
  2. Draft content (style guide loaded above)
  3. Call polish_text() before saving
  4. Call run_vale_check() for final verification
  5. Use save_file() with auto_check_writing=True