SalesSidekick/skills/brand-voice/SKILL.md
Fires on any written output — emails, outreach, LinkedIn posts, business cases, follow-ups. Provides: voice rules, email formatting, vocabulary substitutions, banned phrases, sign-off, and 7-point voice check. Output contract: all written content matches the user's calibrated tone and style.
npx skillsauth add chieflatif/SalesSidekick-Claude-CoWork brand-voiceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tier 3 — This entire file is regenerated during deep personalization Phase 4 based on the AE's communication preferences and writing samples.
Defines the AE's personal communication voice for all written outputs. Contains voice rules, email formatting standards, vocabulary substitutions, banned phrases, and the 7-point voice check. Ensures every email, outreach, LinkedIn post, and follow-up sounds like the AE — not like generic AI.
Communication style: {{COMMUNICATION_STYLE}}
Default voice (before deep personalization):
After deep personalization, these rules are rewritten based on the AE's actual communication preferences and writing samples.
| Rule | Standard | |------|----------| | Subject lines | Lowercase unless proper nouns. Under 6 words. Specific, not clickbait. | | Length | Under 200 words. If it's longer, it should be a document, not an email. | | Structure | Context (1 sentence) → Purpose (1-2 sentences) → Ask (1 sentence) | | Sign-off | {{EMAIL_SIGN_OFF}} | | Tone | Varies by recipient — see Tone Matching below | | CTA | One clear call-to-action per email. Never more than one. |
Match communication tone to the recipient's role and relationship:
| Audience | Tone | Example | |----------|------|---------| | Champion | Warm, collaborative, insider language | "Hey Sarah — quick update on the POC timeline..." | | Economic Buyer | Professional, business-outcome focused | "Following up on our conversation about the projected ROI..." | | Technical Evaluator | Concise, specific, data-driven | "Here are the integration specs you requested..." | | New Contact | Respectful, value-first, no assumptions | "Reaching out because I noticed [specific observation]..." | | Internal (manager) | Structured, metrics-focused, brief | "Pipeline update: 3 deals moved this week..." |
After deep personalization, this section contains the AE's specific vocabulary preferences.
Default substitutions (before deep personalization):
| Instead of | Use | |-----------|-----| | "Reach out" | "Contact" or "get in touch" | | "Circle back" | "Follow up" or "revisit" | | "Touch base" | "Connect" or "check in" | | "Synergy" | [delete — don't replace, just remove] | | "Leverage" | "Use" or "apply" | | "Bandwidth" | "Capacity" or "time" | | "Deep dive" | "Detailed review" or "analysis" | | "Ping" | "Message" or "email" | | "Loop in" | "Include" or "add" | | "Take offline" | "Discuss separately" | | "Ideate" | "Brainstorm" or "think through" | | "Socialize" | "Share" or "discuss" |
These phrases are NEVER used in any communication, regardless of context:
Default banned list (before deep personalization):
After deep personalization, this list is customized with the AE's personal banned phrases and may add phrases they never want AI to generate.
Run this check on every communication output before presenting:
| # | Check | Question | |---|-------|----------| | 1 | Authenticity | Does this sound like {{AE_NAME}} wrote it, or like a robot? | | 2 | Vocabulary | Are all vocabulary substitutions applied? No banned phrases? | | 3 | Length | Is the email under 200 words? Is the LinkedIn post 150-300 words? | | 4 | Structure | One clear purpose? One clear CTA? | | 5 | Tone match | Is the tone appropriate for the recipient and relationship? | | 6 | Sign-off | Using {{EMAIL_SIGN_OFF}} (or appropriate LinkedIn close)? | | 7 | Filler check | Zero filler phrases? No "I hope," "just wanted to," "I'd love to"? |
Passing score: 7/7 for emails and outreach. 5/7 acceptable for LinkedIn posts (length and sign-off rules differ).
LinkedIn voice differs from email voice:
On the first run of outreach, the user is asked for their typical email tone and optionally provides a sample email. The calibration response is stored here as supplemental voice data:
This supplements the deep personalization voice profile. If outreach runs before deep personalization, calibration data is stored here and merged into the full voice profile when deep personalization completes.
tools
AE professional identity and context used for personalized output across all commands
testing
PptxGenJS pipeline for generating native .pptx presentations with brand tokens, 5 deck templates, and visual QA
development
LinkedIn content framework with 3-Type post structure, hook formulas, cadence goals, and 6-point pre-publish checklist
documentation
Central reference for all Notion database schemas, read/write patterns, account resolution logic, and write failure handling