editorial-voice-shaping

Diagnose and rewrite route copy while preserving authored voice and route fit.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/2zcory/skills --skill editorial-voice-shaping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-voice-shaping
Source: https://github.com/2zcory/skills/tree/main/editorial-voice-shaping
Command: npx skills add https://github.com/2zcory/skills --skill editorial-voice-shaping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a compatibility layer for rewriting route copy with a narrow focus, preserving authored voice and route fit while avoiding broader content-architecture changes.

Core Features & Use Cases

  • Diagnose copy pathologies in route copy and apply a targeted rewrite that preserves voice and route alignment.
  • Provide a concise, publish-ready rewritten text that fits the route and maintains consistent messaging.
  • Use when legacy workflows explicitly request narrow rewrite passes or when a broader content-architecture approach is not desired.

Quick Start

Provide a compact rewrite of the given route copy that improves clarity and preserves the original voice.

Frequently Asked Questions about editorial-voice-shaping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rewrite route copy to reduce AI-like stiffness without losing the original voice?

A targeted route copy rewrite diagnoses text pathologies and applies a narrow pass that reduces robotic stiffness while preserving the authored voice and route alignment. It avoids broader content-architecture changes to maintain messaging consistency.

What is route copy pathology diagnosis and when do I need it?

Route copy pathology diagnosis identifies stiff, mechanical phrasing in public-facing messaging. You need it when legacy workflows request a compatibility layer to improve clarity and reduce AI-like tone while maintaining the original authored voice.

How do I perform a narrow rewrite pass on public-facing messaging?

Perform a narrow rewrite pass by analyzing the existing route copy for stiffness, applying job-first ordering to the corrections, and documenting any residual risks to provide a concise, publish-ready text that fits the route.

Does this copy-editing approach work for legacy content workflows that need a compatibility layer?

Yes, this copy-editing approach is designed for legacy workflows that explicitly request narrow rewrite passes. It provides a compatibility layer that refines public-facing route copy without forcing a full content-architecture overhaul.

What are the limitations of a narrow rewrite pass for voice systems?

The limitation of a narrow rewrite pass is that it intentionally avoids broader content-architecture changes. It focuses strictly on reducing stiffness and preserving voice, meaning structural messaging flaws may require a separate workflow.