Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Messaging Rules Check

ASecurity

Encodes your full writing style guide PLUS your locked messaging decisions as deterministic rules. Every external content output passes through this gate.

7 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsgogitapiperformance

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add unempyd/revenueos --skill messaging-rules-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Messaging Rules Check?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Messaging Rules Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/unempyd-messaging-rules-check/badge)](https://www.skillsdirectory.com/skills/unempyd-messaging-rules-check)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: messaging-rules-check
trigger: sub-skill, runs on every external content output
load-context: communication-style, preferences-and-constraints
inputs: Draft text + intended voice + locked messaging decisions
sub-skills: none
ends-with: Pass | Fail + violation log written to messaging_violation table if Fail
model: deterministic regex + claude-haiku-4-5 for semantic checks
---

# messaging-rules-check

Encodes your full writing style guide PLUS your locked messaging decisions as deterministic rules. Every external content output passes through this gate.

## Hierarchy

When rules conflict, follow the more specific rule.

1. Founder voice (most specific) > Company voice
2. Locked messaging decisions > Writing style guide > humanizer rules
3. Hard punctuation rules (no em dash, no semicolon) always apply

## Locked Company Terminology

[Customize per your company. Examples below from `company-context/communication-style.md`.]

### Must use

- [Your preferred terminology, e.g., "specialized AI workers" instead of "agents" for external use]
- [Your product component names — capitalized, exact spellings]
- [Your preferred verbs]

### Must NOT use

- [Banned company-specific terms]
- [Wrong buyer mentions]
- [Off-brand language]

### Locked numerical facts

- [Your ACV range]
- [Your current ARR]
- [Your customer count]
- [Your accuracy/performance claims]
- [Your founding facts]

### Three differentiators (only these three)

[List the three. Don't list four. Accuracy or another claim is woven through, not its own pillar.]

### Verticals (only these for external content)

[List 3 to 5 verticals. Sub-verticals OK in use-case materials only.]

## Writing Style Guide — Banned Words

The skill regex-scans for these case-insensitive. Auto-fail on any hit. Customize per your voice.

A common B2B marketing voice guide banned word list (most companies should ban most of these):

may, just, very, really, literally, actually, certainly, probably, basically, maybe, delve, embark, enlightening, esteemed, shed light, craft, crafting, imagine, realm, game-changer, unlock, skyrocket, abyss, revolutionize, disruptive, utilize, utilizing, dive deep, tapestry, illuminate, unveil, pivotal, intricate, elucidate, hence, furthermore, harness, exciting, groundbreaking, cutting-edge, remarkable, remains to be seen, glimpse into, navigating, landscape, stark, testament, in summary, in conclusion, moreover, boost, skyrocketing, opened up, powerful, inquiries, ever-evolving, underscore, bolster, foster, leverage, unpack, pave the way, transformative, game-changing, robust, comprehensive, seamless, nuanced (as empty praise), vibrant, multifaceted, holistic

## Banned Phrases

- "In today's fast-paced / rapidly evolving / digital world"
- "It's important / worth noting that"
- "One of the most important / significant / crucial"
- "When it comes to" / "At its core" / "At the end of the day"
- "This is where X comes in" / "Let's break it down" / "Let's get into it"
- "Plays a crucial role in" / "It cannot be overstated"
- "Underscoring the importance of"
- "Highlighting the need for"
- "Reflecting a broader trend toward"
- "Marking a significant shift in"
- "Emphasizing the significance of"
- "Reflecting the continued relevance of"
- "Here's the thing:" / "Here's the problem:" / "Here's what changed:"

## Banned Structures

- "It's not just X, it's Y"
- "Not only X, but Y"
- "This isn't about X. It's about Y."
- "No X. No Y. Just Z."
- "Here's the [noun]:" as a framing device

## Hard Punctuation Rules

- **No em dashes.** Includes unicode em dash, double-hyphen substitute, any variation. Replace with parentheses, commas, or rewrite.
- **No semicolons.** Use commas, periods, or parentheses.

## Formatting Rules

- No hashtags.
- No emoji unless explicitly requested.
- No bold for emphasis in running prose. Bold for labels only.
- Never the "**Bold term:** explanation sentence" list format in prose. Most recognizable AI pattern.
- No nested bullets.
- No headers below H2 in newsletter or prose content.

## Process

### Stage 1: Regex scans (deterministic)

1. Banned word scan (case-insensitive)
2. Banned phrase scan
3. Banned structure scan
4. Em dash detection (unicode `—` plus double-hyphen `--`)
5. Semicolon detection
6. Bold-prose-list pattern detection (`**Word:**` followed by sentence)
7. Locked terminology violation scan
8. Numerical fact violation (claims wrong ACV, wrong customer count, etc.)
9. Differentiator overshoot (more than 3 listed)
10. Vertical violation (non-approved verticals named externally)

### Stage 2: Semantic checks (claude-haiku)

For nuanced cases:

- Buyer mismatch (semantically positions wrong buyer)
- Headcount replacement framing without banned words
- Endorsement-shaped language without disclosure
- Voice fingerprint mismatch (CEO draft sounds like CTO, vice versa)

### Stage 3: Aggregate verdict

If any deterministic check fails OR semantic check returns high-confidence violation:

- verdict: FAIL
- blocks_publish: true
- Write to messaging_violation table
- Return structured violations with suggested fixes

Otherwise:

- verdict: PASS
- blocks_publish: false

## Regeneration loop

If verdict=FAIL:

1. Regenerate the section containing the violation with stricter prompt: "Previous draft contained these violations: [list]. Fix and avoid."
2. Re-check.
3. If second attempt fails: write all violations to messaging_violation table, flag draft for human review, do NOT ship.

## Output

```json
{
  "verdict": "PASS" | "FAIL",
  "violations": [
    {
      "rule": "banned_term:leverage",
      "offending_span": "We leverage [Your Product] to drive efficiency",
      "suggested_fix": "Replace 'leverage' with 'use' or rewrite: 'We use [Your Product] to execute high-judgment workflows.'",
      "severity": "blocking",
      "category": "voice"
    },
    {
      "rule": "em_dash_detected",
      "offending_span": "The locked decisions — done in April — apply",
      "suggested_fix": "Replace em dashes with parentheses: 'The locked decisions (done in April) apply.'",
      "severity": "blocking",
      "category": "punctuation"
    },
    {
      "rule": "bold_prose_list",
      "offending_span": "**Differentiator 1:** Compliance is core...",
      "suggested_fix": "Convert to prose paragraph or remove bold from prose entry. Bold is for labels only.",
      "severity": "blocking",
      "category": "formatting"
    }
  ],
  "regeneration_required": true,
  "blocks_publish": true
}
```

## Why this exists

Your locked messaging decisions took weeks or months to lock down. Your writing style guide took years of practice and feedback to refine. Without enforcement, the AI CMO drifts back to generic AI marketing language inside two weeks. This skill is the structural counterpart of the human discipline that produced the decisions and the style guide.

## Maintenance

When you update your writing style guide or your locked messaging decisions:

1. Update `company-context/communication-style.md`
2. Update this skill's banned word/phrase/structure lists
3. Log the update in CORRECTIONS.md
4. Run `scripts/style-guide-audit.ts` against recent drafts to retroactively flag violations

Attribution

unempydunempyd
View sourceMore from unempyd →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →