agentman-brand-voice

# Agentman Brand Voice & Style Guide v3

This skill governs how we write across **two distinct products** that share a parent brand but serve different audiences.

**Step 1 for every piece of content: Which product is this for?**

---

## Two Products, One Parent Brand

### Agentman.ai — The Agentic Healthcare Platform
- **Audience:** Healthcare practices (1–5 MDs), RCM teams, compliance/IT buyers
- **Promise:** Automate back-office work without losing control
- **Voice mode:** Calm Challenger — healthcare-first, governance-forward, outcome-led
- **Trust threshold:** High. Regulated buyers. Every word must earn trust.

### myAgentSkills.ai — AI Skills for Everyone
- **Audience:** Anyone making AI actually useful — ops teams, marketers, sales, developers, support
- **Promise:** Turn AI from smart to expert with structured skills
- **Voice mode:** Practical Enabler — cross-industry, platform-neutral, builder-friendly
- **Trust threshold:** Moderate. Productivity buyers. Show capability, not compliance.

### The Parent Brand: Agentman (Chain of Agents, Inc.)
- Both products say "from Agentman" — the parent brand carries credibility
- Corporate/investor content follows Agentman.ai voice by default

---

## Shared Voice Principles (Apply to BOTH Products)

These are non-negotiable regardless of which product you're writing for.

### Core Voice Attributes
- **Outcome-first** — lead with what changes for the reader, not features
- **Plain English** — no jargon a front-desk manager couldn't read aloud
- **Calm, earned confidence** — we've done the work, we don't need to shout
- **Reassuring before impressive** — trust first, admiration second

### Lighthouse Belief
**Production AI requires structure. Prompts alone drift.**

Whether it's a healthcare agent or a marketing skill, the same truth holds: unstructured AI is unreliable AI. Structure is what makes AI actually useful in real work.

### Relationship Language
- The customer is the hero
- Agentman / AgentSkills is the guide
- "Works alongside your team," not "replaces"

### Urgency Calibration
**Default:** measured confidence

Allowed:
- "Available today"
- "In production now"
- "Free to start"

Never:
- Scarcity or countdown pressure
- Fear-based urgency
- "Don't get left behind" framing

### Universal Don'ts
- No "AI magic" language
- No unsubstantiated superlatives ("best," "only," "fastest") without evidence
- No emojis in product copy (LinkedIn/social is different — see founder voice)
- No snarky dismissiveness (challenger ≠ arrogant)

---

## Product-Specific Rules: Agentman.ai

> Apply these ONLY when writing for agentman.ai — healthcare pages, security pages, platform pages, sales content, and healthcare-focused blogs.

### Archetype
**Healthcare-First B2B Tech + Calm Challenger**

The battle-tested operator who explains without hype. We challenge demo-ware and black-box AI, but we lead with relief, clarity, and proof — especially for small healthcare teams.

### Audience Calibration: Small Healthcare Practices (1–5 MDs)

Assume the reader is an owner-operator or office manager.

**Hard rules:**
- Lead with *relief*, not category language
- Do not open with platform terminology
- The first paragraph must describe a concrete workflow being removed (e.g., eligibility calls, denial follow-ups)
- Introduce "Agentic Healthcare" only after the problem and relief are clear
- Frame governance as protection, not architecture
- Prefer phrases a front-desk manager could read out loud without stumbling

### Landing Page Order (Healthcare)

Mandatory sequence:
1. Operational pain or relief
2. Specific workflow automation
3. Reassurance (control, review, human-in-the-loop)
4. Differentiation (full stack, lineage)
5. Proof
6. Invitation CTA

### Tone by Page Type

| Page Type | Tone | Notes |
|-----------|------|-------|
| Healthcare solution pages | Calm, practical, empathetic | Time saved, mistakes avoided. Governance = reassurance. |
| Security & governance pages | Factual, non-marketing | What is logged and why. No hype, no bravado. |
| Platform & POV pages | Educational, confident | Challenger tone allowed. Production learnings encouraged. |

### Terminology (Agentman.ai)

**Use:** AI agents, deploy, production, workflows, Agentic Healthcare (capitalized), data lineage, governance

**Avoid:** Marketplace, app store, chatbot, install, e-commerce examples, "AI magic"

### First-Paragraph Test (Healthcare)

Before finalizing healthcare copy, verify:
- The first paragraph contains no platform jargon
- The reader can identify a specific task that goes away
- Control or review is mentioned as reassurance

If this test fails, rewrite the opening.

### North Star Test
**Would a 2-MD practice trust this after 30 seconds of reading?**
If not, simplify and lead with relief.

---

## Product-Specific Rules: myAgentSkills.ai

> Apply these ONLY when writing for myagentskills.ai — the skills registry, MCP servers directory, connect/create pages, and skills-focused blogs or social.

### Archetype
**Practical Enabler + Builder's Companion**

The knowledgeable colleague who shows you how to make AI actually do the work — not just talk about it. We bridge the gap between smart AI and useful AI with structured skills anyone can use.

### Audience Calibration: Cross-Industry Practitioners

The reader could be a marketer, sales rep, support lead, developer, accountant, or ops manager. They're AI-curious but frustrated that AI doesn't follow their procedures.

**Hard rules:**
- Lead with the *gap* — AI is smart but doesn't know their work
- Use cross-functional examples, not just healthcare
- Platform-neutral framing: "Works in Claude, ChatGPT, and Agentman Agents"
- Skills are the hero, not the platform
- Emphasize customization: "clone and make it yours"
- Never pressure — invitation only

### Landing Page Order (Skills)

Recommended sequence:
1. The gap (smart ≠ useful)
2. What skills are (not prompts — structured intelligence)
3. Concrete example of a skill in action
4. Breadth (categories, count)
5. Platform compatibility
6. Build your own / customize
7. Invitation CTA

### Tone by Page Type

| Page Type | Tone | Notes |
|-----------|------|-------|
| Homepage / hero | Confident, practical | "Your AI is smart. Make it an expert." is the right register. |
| Skills registry | Functional, clean | Let the skills speak. Minimal editorial. |
| MCP servers directory | Functional, clean | Directory energy. Brief descriptions, easy scanning. |
| Connect / Create pages | Encouraging, builder-friendly | "No code required" energy. Welcoming to non-technical users. |
| Skills-focused blogs | Educational, enabling | How-to energy. Show people what's possible. |

### Terminology (myAgentSkills.ai)

**Use:** Skills, skill registry, connect, create, clone, customize, structured intelligence, production-ready, cross-platform

**Allowed (unlike Agentman.ai):** Browse, registry, e-commerce examples, cross-industry examples

**Avoid:** Marketplace, app store, "AI magic," hype language, scarcity

### Quality Bar Test (Skills)

Before finalizing myAgentSkills copy, verify:
- A non-technical reader understands what a skill does in one sentence
- The copy doesn't assume the reader is a developer
- At least one concrete example shows a skill doing real work
- Platform compatibility is mentioned but not the headline

### North Star Test
**Would a marketing manager with no dev team think "I can use this today"?**
If not, simplify and show a concrete example.

---

## Where the Products Overlap

Some content references both products. Rules for overlap:

### Skills mentioned on Agentman.ai
- Frame skills as the intelligence layer inside Agentman agents
- Don't send healthcare visitors to myAgentSkills.ai — keep them in the healthcare context
- Example: "Agentman agents use structured skills to follow your procedures exactly."

### Healthcare skills on myAgentSkills.ai
- Healthcare is one category among many — don't lead with it
- The CO-50 denial example is a great proof point but shouldn't dominate
- Example: "From healthcare denials to sales discovery calls — skills teach AI how your organization does the work."

### Agentman mentioned on myAgentSkills.ai
- "from Agentman" in the nav is sufficient — don't over-explain
- Link to agentman.ai for people who want the full platform
- myAgentSkills.ai should feel like its own product, not a feature page

---

## Challenger Tone: Scoping Rules

| Context | Challenger Allowed? | Notes |
|---------|-------------------|-------|
| Agentman.ai — healthcare pages | Muted | Calm confidence only |
| Agentman.ai — security pages | No | Factual, non-marketing |
| Agentman.ai — platform/POV pages | Yes | Educational challenger |
| myAgentSkills.ai — homepage | Light | "Smart vs. useful" gap is challenger-light. Good. |
| myAgentSkills.ai — registry/directory | No | Functional pages, no editorial |
| Founder content (LinkedIn, blogs) | Full | Strongest challenger voice lives here |

---

## Founder Voice (Prasad)

Founder voice is intentionally stronger, more contrarian, and more opinionated than either product's pages.

**Where it applies:** LinkedIn posts, thought leadership blogs, keynotes, POV essays

**Where it does NOT apply:** Healthcare solution pages, security pages, core landing pages for either product, skills registry

**Rule:** Founder-level provocation should never be the first impression for healthcare buyers OR skills registry visitors.

---

## Quick Decision Tree

```
What are you writing?
│
├─ For agentman.ai?
│  ├─ Healthcare page → Calm, relief-first, governance as reassurance
│  ├─ Security page → Factual, non-marketing
│  └─ Platform/POV → Educational challenger, production learnings
│
├─ For myagentskills.ai?
│  ├─ Homepage → Confident, practical, cross-industry
│  ├─ Registry/Directory → Functional, clean, minimal editorial
│  └─ Connect/Create → Encouraging, builder-friendly
│
├─ Founder content (LinkedIn, blog)?
│  └─ Full challenger voice, personal stories, contrarian takes
│
└─ Corporate/investor?
   └─ Default to Agentman.ai voice
```