---
name: raven-essay-audit
description: Run an essay (or batch) through Raven's UX-writing and voice systems — produces scorecard + cross-cutting flags
---

# Raven Essay Audit

Audit one or more drafted essays (application "Why X" essays, doorman copy, microcopy, anything user-facing in Andrew's voice) against Raven's content systems. Triggered by `/raven-essay-audit <path>` or "Raven audit this essay".

## Input

One thing: a **file path** (single essay) or **directory path** (batch — audits every `.md` inside).

## Procedure

### 1. Load the source material

Read the essay(s). Note word count and structure (opening, body, close).

### 2. Pull Raven's content systems

Use the raven MCP tools in parallel:

- `mcp__raven__get_content_principles` — UX-writing principles (clarity, voice, scannability, etc.)
- `mcp__raven__get_content_system` for each of: Mailchimp, Atlassian, Intuit
- `mcp__raven__get_content_pattern` if a specific pattern (e.g. "personalized opener", "social proof") is relevant to the essay's purpose

If a system isn't available, use `mcp__raven__list_content_systems` to discover what is.

### 3. Score each essay

Per essay, produce:

```
## <Essay name>  (<word count>w)

### Scorecard
- Clarity: X/10 — <one-line why>
- Voice (Andrew's): X/10 — <one-line why>
- Specificity / proof: X/10 — <one-line why>
- Scannability: X/10 — <one-line why>
- Opening strength: X/10 — <one-line why>
- Close strength: X/10 — <one-line why>

### Flagged edits
1. **<Line or phrase>** → suggested change. Why: <Raven principle>.
2. ...

### Strong as-is
- <Line that lands>
```

### 4. Cross-cutting flags (only if batch)

When auditing multiple essays in one run, surface patterns:

```
## Cross-cutting flags

- **Passive openers** in N/M essays — list them. Rule: lead with "I" + active verb.
- **Brand-name leakage** — flag any aesthetic-inspiration brand mentioned by name (memory: `feedback_brand_references.md`).
- **Inconsistent self-description** — if some essays say "Staff" and others say "Senior Staff," flag (memory: `user_role.md` — Senior Staff is correct).
- **Cover-letter shape** in any essay — flag for rewrite (memory: `feedback_no_cover_letters.md`).
- **"AI-native maker" tagline** — used N times across batch. Once per essay is the sweet spot; flag if over- or under-used.
```

### 5. Write the audit file

Save to `/tmp/drafts/YYYY-MM-DD-essays-raven-audit.md` (or `-<slug>-raven-audit.md` if Andrew specified a context).

Open in Zed:
```bash
open -a Zed /tmp/drafts/YYYY-MM-DD-essays-raven-audit.md
```

### 6. Report back

```
## Raven audit complete

- Audited: N essays
- Average score: X/60
- Highest: <name> (X/60)
- Lowest: <name> (X/60) — most leverage here
- Cross-cutting flags: <count> — top one: <name>
- Open in Zed: <path>

Want me to apply the flagged edits across the batch?
```

If Andrew says "I agree with all of them" or similar, apply the edits in one pass and report the diff.

## Notes

- The first time per session, expect the Raven MCP calls to be slow (cold). Subsequent calls in the same session are fast.
- If a Raven MCP call fails, fall back to the content principles already encoded in Andrew's CLAUDE.md (D4D framework, Ladder of Impact, terse-communication rules) and note the fallback in the report.
- Per Andrew's CLAUDE.md "Quoted-copy typos" rule: if the essay contains copy he explicitly pasted, never auto-fix typos — flag in the scorecard with "say 'fix all' and I'll clean every spot."
