voice-check
$
npx mdskill add lyndonkl/claude/voice-checkAligns drafts to writer voice by flagging forbidden phrases.
- Detects non-canonical phrasing in draft text.
- Depends on voice-profile.md for forbidden phrase rules.
- Matches text patterns using word-boundary regex.
- Outputs flagged phrases with suggested rewrites.
SKILL.md
.github/skills/voice-checkView on GitHub ↗
---
name: voice-check
description: Scans a substacker draft line-by-line against the canonical voice-profile.md don't-list and signature moves. Emits phrase-level flags with location, quoted phrase, violation type, voice-profile citation, and up-to-2 suggested rewrites per flag. Use as pass-2 skill (voice) after structural-review completes, when a draft reads competent but not in the writer's voice, or when the writer asks "does this sound like me?" Trigger keywords: voice check, delve, unpack, paradigm shift, sounds AI, does this sound like me, voice violation.
---
# Voice Check
## Table of Contents
- [Workflow](#workflow)
- [Don't-list regex bank](#dont-list-regex-bank)
- [Worked example](#worked-example)
- [Guardrails](#guardrails)
**Related skills:** Called by the Editor after `structural-review`. Runs alongside `hedge-detector`, `slop-detector`, `citation-form-check`. Each skill owns a specific band of voice issues; this one handles explicit don't-list phrase matches.
## Workflow
```
Voice check draft D:
- [ ] Step 1: Load voice-profile.md (global) + voices/{section}.md (if applicable)
- [ ] Step 2: Extract the don't-list as a regex bank
- [ ] Step 3: Scan draft; match each regex with word boundaries
- [ ] Step 4: For each match: record {line, quoted phrase, violation, voice-profile citation, 2 rewrite options}
- [ ] Step 5: Emit phrase-flags table
```
## Don't-list regex bank
From `voice-profile.md` §10 (Voice don'ts). Word-boundary enforced.
| Violation | Regex | Rewrite hint |
|---|---|---|
| `delve` | `\bdelve(s|d|ing)?\b` | replace with specific verb |
| `unpack` | `\bunpack(s|ed|ing)?\b` | replace with specific verb |
| `dive into` | `\bdive\s+into\b` | replace with specific verb |
| `let's explore` | `\blet'?s\s+(explore|dive)` | delete; open with confession |
| `at the end of the day` | `\bat\s+the\s+end\s+of\s+the\s+day\b` | delete clause |
| `game-changer` | `\bgame[-\s]?changer\b` | name the specific change |
| `paradigm shift` | `\bparadigm\s+shift\b` | name the shift explicitly |
| `under the hood` | `\bunder\s+the\s+hood\b` | replace with "mechanically" or delete |
| `in today's fast-paced world` | `in\s+today'?s\s+(fast[-\s]?paced\s+)?world` | delete; open with a dated concrete fact |
| `AI is transforming` | `(?i)AI\s+is\s+transforming` | delete generic framing; open with confession |
| emoji | `[\u{1F300}-\u{1FAFF}\u{2600}-\u{27BF}]` | delete |
| exclamation | `!` (in body, not quotes) | convert to period |
| `I think` (as hedge) | `\bI\s+think\b` (when followed by a claim, not a question) | commit OR specific hedge |
| `clearly` / `obviously` / `simply` (as persuasion) | `\b(clearly|obviously|simply)\b` | delete or name the step |
| custom CTA | `subscribe\b.*(resonated|more|stay\s+tuned)` | delete; Substack boilerplate is fine |
Section overlays can add or override entries. If `voices/kalshi-log.md` bans "generalizing to other sports", add that rule.
## Worked example
**Draft excerpt**:
> In today's rapidly evolving AI landscape, let's unpack why RAG beats fine-tuning. At the end of the day, RAG is a game-changer. Let's dive into the details!
**Flags (all tier-1)**:
| loc | quote | violation | citation | rewrites |
|---|---|---|---|---|
| P1 S1 | "In today's rapidly evolving AI landscape" | generic opener | voice-profile §10 don't #2 | (a) delete; (b) replace with a dated concrete fact |
| P1 S1 | "let's unpack" | don't-list | §10 don't #1 | (a) "Here is the mechanism" (b) delete |
| P1 S2 | "At the end of the day" | don't-list | §10 don't #1 | (a) delete clause |
| P1 S2 | "game-changer" | don't-list | §10 don't #1 | (a) "it cuts token budget by 40% on our traces" (b) "it avoids a retrain" |
| P1 S3 | "Let's dive into" | don't-list | §10 don't #1 | (a) "Here is what actually happens" (b) delete |
| P1 S3 | "!" (exclamation) | don't-list | §10 don't #8 | (a) period |
Six tier-1 flags in three sentences → triggers Editor must-not #13 (≥3 tier-1 voice violations = no-go).
## Guardrails
1. Every flag must cite a voice-profile line. No flag without citation.
2. Regex must have word boundaries; avoid false positives (e.g., "undelete" shouldn't match `delve`).
3. Section overlays extend but never override global don'ts — an overlay cannot *allow* a global don't.
4. Exclamation-point rule excludes quoted dialogue and code fences.
5. "I think" is flagged only when followed by a claim. "I think so, but I'm not sure" is a sentence of quiet agreement, not a hedge on a claim.
6. Max 2 rewrite options per flag.
## Quick reference
- Input: draft + voice-profile + optional overlay.
- Output: phrase-flags table in the voice pass.
- Complements `hedge-detector` (hedging) and `slop-detector` (structural voice).
More from lyndonkl/claude
- abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
- academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
- adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
- adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
- alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
- analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
- answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
- attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
- auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
- auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".