How do I install the Verbal skill?

Run npx skillmds@latest add bromso/verbal 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.

What does the Verbal skill do?

Develop brand voice, tone, messaging pillars, and verbal identity It is listed under Coding & Dev Tools on SkillMD.

Is Verbal safe to use?

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

Which AI agents work with Verbal?

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 Verbal free to use?

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

Who published Verbal?

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

Verbal by bromso — Agent Skill

Name: Verbal
Author: bromso

File contents

Verbal Identity

Develop the verbal identity for "$ARGUMENTS". Create the voice, tone, messaging framework, and language guidelines that bring the brand personality to life in words.

Prerequisites

Read .metapowers/branding/$ARGUMENTS/01-discover.md and .metapowers/branding/$ARGUMENTS/02-strategy.md. If 02-strategy.md does not exist, tell the user:

Phase 2 (Strategy) has not been completed for "$ARGUMENTS". Run /branding:strategy $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/branding/$ARGUMENTS/skip-log.md.

Process

Read context files:
- Read .metapowers/branding/$ARGUMENTS/01-discover.md for audience insights
- Read .metapowers/branding/$ARGUMENTS/02-strategy.md for personality, values, and positioning
Define brand voice:
- Voice is consistent — it's WHO the brand is
- Describe the voice using the personality traits from Strategy
- Provide "We are / We are not" examples
- Example: "We are confident but not arrogant. We are friendly but not casual."
Define tone variations:
- Tone adapts to context — it's HOW the brand speaks in different situations
- Define tone for: marketing, support, social media, formal communications, error messages
- For each context: tone description + example copy
Create messaging pillars:
- 3-5 key messages the brand consistently communicates
- For each pillar: headline, supporting statement, proof point
Develop tagline/endline options:
- Generate 3-5 tagline candidates
- Evaluate each against the positioning and personality
- Recommend the strongest option
Language guidelines:
- Preferred vocabulary and phrases
- Words and phrases to avoid
- Grammar and style preferences (e.g., Oxford comma, contractions, capitalization)
Write the artifact to .metapowers/branding/$ARGUMENTS/03-verbal.md

Output

The verbal identity written to .metapowers/branding/$ARGUMENTS/03-verbal.md. Present a summary to the user highlighting:

Voice description in one sentence
Top tagline recommendation
Messaging pillars overview

---name: verbaldescription: Develop brand voice, tone, messaging pillars, and verbal identity---# Verbal IdentityDevelop the verbal identity for "$ARGUMENTS". Create the voice, tone, messaging framework, and language guidelines that bring the brand personality to life in words.## PrerequisitesRead `.metapowers/branding/$ARGUMENTS/01-discover.md` and `.metapowers/branding/$ARGUMENTS/02-strategy.md`. If `02-strategy.md` does not exist, tell the user:> Phase 2 (Strategy) has not been completed for "$ARGUMENTS". Run `/branding:strategy $ARGUMENTS` first, or use `--skip-checks` to bypass.If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/branding/$ARGUMENTS/skip-log.md`.## Process1. **Read context files:** - Read `.metapowers/branding/$ARGUMENTS/01-discover.md` for audience insights - Read `.metapowers/branding/$ARGUMENTS/02-strategy.md` for personality, values, and positioning2. **Define brand voice:** - Voice is consistent — it's WHO the brand is - Describe the voice using the personality traits from Strategy - Provide "We are / We are not" examples - Example: "We are confident but not arrogant. We are friendly but not casual."3. **Define tone variations:** - Tone adapts to context — it's HOW the brand speaks in different situations - Define tone for: marketing, support, social media, formal communications, error messages - For each context: tone description + example copy4. **Create messaging pillars:** - 3-5 key messages the brand consistently communicates - For each pillar: headline, supporting statement, proof point5. **Develop tagline/endline options:** - Generate 3-5 tagline candidates - Evaluate each against the positioning and personality - Recommend the strongest option6. **Language guidelines:** - Preferred vocabulary and phrases - Words and phrases to avoid - Grammar and style preferences (e.g., Oxford comma, contractions, capitalization)7. **Write the artifact** to `.metapowers/branding/$ARGUMENTS/03-verbal.md`## OutputThe verbal identity written to `.metapowers/branding/$ARGUMENTS/03-verbal.md`. Present a summary to the user highlighting:- Voice description in one sentence- Top tagline recommendation- Messaging pillars overview

Frequently asked questions

Verbal