editorial-review-report

Aggregate comment-annotation categories across editorial-review workflows to surface operator corrections.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-review-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-review-report
Source: https://github.com/oletizi/audiocontrol.org/tree/main/.claude/skills/editorial-review-report
Command: npx skills add https://github.com/oletizi/audiocontrol.org --skill editorial-review-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Aggregate comment-annotation categories across completed editorial-review workflows to surface which voice-skill principles are producing the most operator corrections. Read-only; does not change the voice skills.

Core Features & Use Cases

  • Signal aggregation across editorial-review workflows to reveal voice-skill drift patterns and operator corrections.
  • Per-site scoping via --site to analyze a single site, and via --include-in-flight to include non-terminal drafts.
  • Read-only reporting that informs prioritization without editing any voice skills.

Quick Start

Run /editorial-review-report to generate the current drift signal for all sites, or use --site <slug> to scope to one site.

Frequently Asked Questions about editorial-review-report

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

FAQPage Schema
How do I track voice-skill drift patterns from editorial review comments?

You can scope drift signal aggregation to a single site by passing the --site argument with the site slug. Omitting this argument generates the current drift signal report across all sites by default.

Can I include in-flight drafts when generating an editorial review report?

You can include in-flight drafts in the editorial review report by passing the --include-in-flight flag. This broadens the drift signal by incorporating non-terminal drafts alongside completed workflows into the aggregated report.

Does the editorial review report modify active voice skills?

The editorial review report does not modify active voice skills because it is a strictly read-only reporting tool. It only surfaces operator correction patterns to inform prioritization without editing underlying voice skills.

What is the best way to prioritize voice-skill principles needing updates based on operator corrections?

The best way to prioritize voice-skill updates is to aggregate comment-annotation categories from completed editorial-review workflows. This reveals which principles produce the most operator corrections and generates a read-only drift signal report for prioritization.