editorial-standards

Review technical documents against editorial standards and style guides.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/JonnyCBB/claude-code-config --skill editorial-standards-jonnycbb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-standards
Source: https://github.com/JonnyCBB/claude-code-config/tree/main/plugins/jiffy-toolkit/skills/editorial-standards
Command: npx skills add https://github.com/JonnyCBB/claude-code-config --skill editorial-standards-jonnycbb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides reference material for applying editorial standards and professional writing practices to technical documents, improving clarity, accuracy, and consistency across reviews.

Core Features & Use Cases

  • Central reference for editorial review based on professional editing standards and authoritative style guides.
  • Contains evaluation dimensions (content, style, mechanics, consistency, accessibility) and document-type standards (RFCs, READMEs, tutorials, API docs), plus a decision framework to determine when to edit versus preserve.
  • Supports practitioners with recommended reading patterns and plain-language rules to improve readability and accessibility in technical documents.

Quick Start

Review a technical document using the included editorial-dimensions and decision-framework guidance to identify actionable edits and alignment with style guides.

Frequently Asked Questions about editorial-standards

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

FAQPage Schema
How do I review technical documents for editorial consistency and readability?

Review technical documents for editorial consistency by applying established style guides across content, style, mechanics, and accessibility dimensions. Structured evaluation frameworks flag actionable edits and alignment issues for technical writing.

What editorial standards should I apply when writing RFCs and API documentation?

Apply editorial standards for RFCs and API documentation using evaluation dimensions for content accuracy, style consistency, mechanics, and accessibility. Authoritative style guides provide structured criteria to review and refine technical documentation.

How can I improve accessibility and readability in technical writing?

Improve accessibility and readability in technical writing by applying plain-language rules and recommended reading patterns. These editorial standards provide structured frameworks to evaluate and enhance document clarity for diverse audiences.

Can I use this editorial review framework for tutorials and READMEs?

Yes, the editorial review framework supports tutorials and READMEs alongside RFCs and API documentation. Document-type standards provide specific evaluation criteria for content, style, mechanics, consistency, and accessibility across various technical document formats.

When should I edit versus preserve content during a document review?

Determine when to edit versus preserve content using the decision framework within the editorial standards. This framework guides reviewers in identifying which sections require actionable edits and which should remain unchanged to maintain technical accuracy.

What is the best way to evaluate technical writing quality across multiple dimensions?

Evaluate technical writing quality across multiple dimensions including content, style, mechanics, consistency, and accessibility. The editorial standards framework provides structured criteria and references to authoritative style guides for comprehensive document assessment.