agentman-landing-page-writer

# Agentman Landing Page Writer

This skill is a **structural enforcement layer** for all Agentman landing pages. It does not define voice (handled by `agentman-brand-voice`). Instead, it enforces **order of persuasion**, **calm confidence**, and **anti-hype guardrails**.

Use this skill **whenever generating any landing page or top-level website copy**.

---

## When to Use

Use this skill when writing:
- Homepage copy
- /healthcare overview pages
- Individual agent pages (eligibility, denials, voice, etc.)
- Security & governance pages
- Any page intended to convert a healthcare buyer

Do NOT use for blogs, LinkedIn posts, or founder POV content.

---

## Mandatory Page Structure (Non-Negotiable)

All landing pages must follow this order:

1. **Relief-first opening**
   - Describe operational pain or relief
   - No platform or category language

2. **Concrete work removed**
   - Name specific workflows that disappear
   - Speak in plain operational language

3. **Reassurance & control**
   - Human-in-the-loop
   - Review, approval, visibility

4. **Differentiation**
   - Full stack
   - Governance, lineage, lifecycle

5. **Proof**
   - Metric, timeframe, or concrete example

6. **Invitation CTA**
   - Calm, non-urgent

If the output does not follow this order, it is invalid.

---

## First-Paragraph Rule (Hard Constraint)

The first paragraph must:
- Contain **no platform terminology**
- Contain **no category language** (e.g., Agentic Healthcare)
- Describe a **specific task that goes away**

If this rule is violated, rewrite the opening.

---

## Calm Confidence Enforcement

This skill blocks:
- Hype language ("revolutionary", "game-changing")
- Urgency language ("act now", "limited time")
- Excessive exclamation points
- Anthropomorphizing agents as people

Tone should feel like:
> "We’ve seen this problem many times. This is how teams fix it."

---

## Marketplace & App Store Language (Banned)

The following concepts must NOT appear:
- Marketplace
- App Store
- Browse agents
- Buy agents
- Install agents

Redirect language toward:
- Workflows
- Operational support
- Runs alongside your systems
- Configured for your practice

---

## Platform Language Timing

Platform concepts may only appear **after** relief and reassurance are established.

Allowed later:
- Agentic Healthcare
- Agent lifecycle
- Governance
- Data lineage

Never lead with these.

---

## Audience Calibration (1–5 MD Practices)

Assume the reader is:
- An owner-operator physician, or
- A front-desk / office manager

Guidelines:
- Write in language that can be read out loud
- Prefer concrete examples over abstractions
- Frame governance as protection, not architecture
- Avoid enterprise or IT jargon

---

## Output Expectations

The output should:
- Feel calm and trustworthy
- Make relief obvious within 30 seconds
- Justify trust without overselling
- Invite conversation, not pressure

---

## Example (Opening Only)

**Good:**
> Every day, practices lose hours to eligibility checks, follow-ups, and phone calls that pull staff away from patients.

**Bad:**
> Agentman is the Agentic Healthcare platform built on a full agent lifecycle architecture.

---

## Final Check Before Output

Before returning copy, verify:
- [ ] First paragraph contains no platform jargon
- [ ] At least one workflow is named
- [ ] Governance appears as reassurance
- [ ] CTA is calm and invitational

If any box is unchecked, revise.