published-voice

Judge or draft published prose against a ratified voice calibration for articles, site copy, and social teasers.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill published-voice-tedeuxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: published-voice
Source: https://github.com/tedeuxx/tadeumendonca-skills/tree/main/skills/published-voice
Command: npx skills add https://github.com/tedeuxx/tadeumendonca-skills --skill published-voice-tedeuxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting and reviewing content in a specific owner's voice produces inconsistent results when the writer and reviewer apply different mental rules. This Skill gives both personas one shared, ratified calibration — the goal, the filter, the subject bound, corpus evidence, register constraints, and teaser arc — so a review produces a conflict against the same ruler rather than two unrelated opinions. ## Core Features & Use Cases - Voice calibration rules: Encodes the owner's stated directives (proximity and informality, no authority positioning, touching the reader's personal side) with precedence rules resolving conflicts between the platform architecture page, the owner's live interview statements, and his 26-article Medium corpus. - Register as mechanism: Defines the 'poetry for developers' register as four checkable constraints — claims resolving to openable files, admissions that cost the author, limits stated first, and short declaratives after long technical passages — rather than an unreproducible style. - Review-ready findings: Gives a content-reviewer persona ranked, citable rules (including numbered downstream rules) to raise findings against drafts of articles, site copy, and LinkedIn/X teasers before they reach the owner. - Use Case: A drafting persona writes a diary-style article about the owner's agent loop; a reviewing persona checks it against the same file and flags a passage that positions the author instead of delivering value, citing the exact rule it violates. ## Quick Start Review this draft article against the published-voice calibration and list every passage that violates a ranked rule.

Frequently Asked Questions about published-voice

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

FAQPage Schema
How do I review a draft against a defined author voice?

Load the calibration file and check the draft against each ranked rule: the goal directives, the journey rule, the four register constraints, and the sourcing constraint. Report findings as citations of specific rules rather than general impressions.

How to keep a writer and reviewer consistent when editing content?

Give both personas the same single calibration document instead of separate copies of the rules. Two readers of one rule produce a conflict that can be resolved; two readers of two copies produce unrelated opinions.

What makes a technical article register reproducible across writers?

Define the register as checkable constraints rather than a style description: every claim resolves to a file the reader can open, admissions cost the author, limits are stated before the reader finds them, and short declaratives follow long technical passages.

Can a draft originate opinions or experiences for the author?

No. The sourcing constraint requires drafts to shape, cut, and structure material the owner already has, never to originate it. When material is missing, the draft stops and states plainly what is needed from the owner.

When should voice calibration rules not be extracted into a shared skill?

When changing a persona's mandate would change the rule, the rule is not transversal and belongs in that persona's brief. Extraction is justified only when a second consumer, such as a reviewer, is decided and next.