How do I install the Brand Voice For Bouts skill?

Run npx skillmds add nickgallick/brand-voice-for-bouts in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Brand Voice For Bouts safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brand Voice For Bouts?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brand Voice For Bouts free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Brand Voice For Bouts?

nickgallick (@nickgallick) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brand Voice For Bouts by nickgallick

Name: Brand Voice For Bouts
Rating: 4.666666666666667 (3 reviews)
Author: nickgallick

Brand Voice For Bouts

The specific voice, tone, writing rules, approved vocabulary, and forbidden phrases for all Bouts content. Use when writing or reviewing any Bouts copy — landing pages, social posts, emails, reports, DMs, press pitches — to ensure the brand sounds authoritative, data-driven, and impossible to confuse with generic AI marketing.

nickgallick b088503 2.5 KB Updated Sep 8, 2026 0 repo stars

File contents

Brand Voice for Bouts

Voice attributes

Authoritative but not arrogant: Show the data. Let it speak. Do not claim to be the only benchmark that matters.
Technical but accessible: A developer understands every blog post. A non-developer understands every tweet. Same data, different depth.
Competitive but fair: Celebrate great agent performance. Never mock poor performance. Analyze, do not ridicule.
Data-driven, never hype: Every claim has a number. "Agents improved" → "Agents improved 18% on Recovery scores this month."
Insider language: Use platform terms naturally — Blacksite Debug, CDI, Recovery Judge, Versus, Abyss, Integrity Judge. This builds brand vocabulary.

What we NEVER say

"The best AI benchmark"
"Unbeatable" / "revolutionary" / "game-changing"
"Our AI is smarter than X"
"Guaranteed results"
Any vague superlative without a data point

What we ALWAYS include

Specific numbers: "23% solve rate," "379-point ELO spread," "15 failure archetypes"
Attribution: "According to this week's challenge data…" / "The Bouts AI Agent Index shows…"
Methodology references: "Scored across 5 independent judge lanes…" / "Using contamination-resistant challenge generation…"

Writing rules

Lead with the insight, not the setup
One idea per paragraph, one point per tweet
Use Bouts terminology naturally
Include a data point in every post
End with a question or call-to-action when appropriate
Short sentences. Active voice.

Sample rewrites

Wrong: "Our amazing AI platform helps developers understand their agent performance in a revolutionary new way."

Right: "Bouts scores AI agents across 5 independent judge lanes — not just did it work, but how it worked and whether you'd trust it in production."

Wrong: "We're the best AI benchmark available today."

Right: "Static benchmarks cluster top models within 5-8%. Bouts produces 379-point ELO spreads. The difference is what you measure."

Wrong: "Check out our new challenge!"

Right: "This week's Blacksite Debug has a 12% solve rate so far. Here's what the 88% are getting wrong."

---name: brand-voice-for-boutsdescription: The specific voice, tone, writing rules, approved vocabulary, and forbidden phrases for all Bouts content. Use when writing or reviewing any Bouts copy — landing pages, social posts, emails, reports, DMs, press pitches — to ensure the brand sounds authoritative, data-driven, and impossible to confuse with generic AI marketing.---# Brand Voice for Bouts## Voice attributes- **Authoritative but not arrogant:** Show the data. Let it speak. Do not claim to be the only benchmark that matters.- **Technical but accessible:** A developer understands every blog post. A non-developer understands every tweet. Same data, different depth.- **Competitive but fair:** Celebrate great agent performance. Never mock poor performance. Analyze, do not ridicule.- **Data-driven, never hype:** Every claim has a number. "Agents improved" → "Agents improved 18% on Recovery scores this month."- **Insider language:** Use platform terms naturally — Blacksite Debug, CDI, Recovery Judge, Versus, Abyss, Integrity Judge. This builds brand vocabulary.## What we NEVER say- "The best AI benchmark"- "Unbeatable" / "revolutionary" / "game-changing"- "Our AI is smarter than X"- "Guaranteed results"- Any vague superlative without a data point## What we ALWAYS include- Specific numbers: "23% solve rate," "379-point ELO spread," "15 failure archetypes"- Attribution: "According to this week's challenge data…" / "The Bouts AI Agent Index shows…"- Methodology references: "Scored across 5 independent judge lanes…" / "Using contamination-resistant challenge generation…"## Writing rules- Lead with the insight, not the setup- One idea per paragraph, one point per tweet- Use Bouts terminology naturally- Include a data point in every post- End with a question or call-to-action when appropriate- Short sentences. Active voice.## Sample rewrites**Wrong:**"Our amazing AI platform helps developers understand their agent performance in a revolutionary new way."**Right:**"Bouts scores AI agents across 5 independent judge lanes — not just did it work, but how it worked and whether you'd trust it in production."---**Wrong:**"We're the best AI benchmark available today."**Right:**"Static benchmarks cluster top models within 5-8%. Bouts produces 379-point ELO spreads. The difference is what you measure."---**Wrong:**"Check out our new challenge!"**Right:**"This week's Blacksite Debug has a 12% solve rate so far. Here's what the 88% are getting wrong."

Frequently asked questions