writing-quality-editor

Compose, assess, revise, and adapt user-facing writing while preserving facts, quotations, and identifiers.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill writing-quality-editor-ravenslight2010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-quality-editor
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/writing-quality-editor
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill writing-quality-editor-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing user-facing text often introduces subtle errors: numbers get changed, warnings get softened, commands get altered, and unsupported claims get strengthened. This Skill provides a disciplined workflow for drafting, reviewing, revising, and adapting writing without changing what the source is allowed to mean. ## Core Features & Use Cases - Four explicit modes: Compose new text from supplied facts, Assess problems without rewriting, Revise text in the same language, or Adapt it for another locale or audience. - Invariant preservation: Locks quotations, citation markers, numbers, units, dates, commands, code, error codes, product names, warnings, and obligation strength (must/may/should/never) so edits never distort meaning. - Content profiles: Tailored guidance for documentation and runbooks, release notes and reports, app UI copy, error messages, and public or marketing copy. - Use Case: A manager asks you to polish a release note claiming "all devices always sync instantly" while tests passed 87/90. The Skill preserves the exact 87/90 figure, flags the unsupported universal claim, and revises the surrounding prose without strengthening the claim. ## Quick Start Ask the assistant to revise the attached setup guide for new staff while keeping every command, quoted policy sentence, error code, and safety warning unchanged.

Frequently Asked Questions about writing-quality-editor

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

FAQPage Schema
How do I revise documentation without changing its meaning?

Use the Revise mode, which records facts, quotations, numbers, commands, and warnings as invariants before editing. The Skill improves structure and clarity locally while confirming that locked technical content and obligation strength remain unchanged.

How to review writing without rewriting it?

Request an assessment rather than a fix. Assess mode lists issues by impact, explains the effect on the reader, and deliberately does not supply replacement text or edit files, since a review request does not authorize edits.

Can AI editing preserve exact commands and error codes?

Yes. Commands, code, error codes, product names, and stable identifiers are treated as locked invariants that must not be altered or translated. For substantial revisions, the Skill states whether these elements were preserved.

What is the difference between revising and adapting text?

Revise improves text within the same language, while Adapt rewrites it for another language, locale, or audience rather than translating mechanically. Both modes preserve factual content, conditions, and warnings.

When should writing edits not be applied automatically?

Edits should not be applied when a request asks only for review, when factual support for a claim is uncertain, or when the requested action conflicts with editing authority. In those cases the Skill asks one focused question or routes the claim for verification first.