muvon/octomind-tap/content-audit

Overview

The shared rubric for scoring any content the system writes. The audit agent renders read-only reports from it; the editor agent uses the same diagnosis to drive rewrites. The harness detects the content type, routes to the platform skill, and grades with per-axis scores plus a prioritized findings list. It never writes to the source file.

Mental model

An audit is intent-versus-execution: what does this content type need to win, what does this draft actually deliver, where is the gap, and how cheap is each fix.

Three constraints keep the harness useful instead of confusing:

• Platform skills own the rules; the harness owns the grading. social-x knows what good X looks like; this skill knows how to count, weight, and report what it finds. Never restate platform rules here — read them from the activated skill.
• One canonical report shape across every content type. Same headers, same severity tiers, same axis vocabulary. Only the weights on each axis change per content type. Skim-able regardless of input.
• Read-only — the auditor renders the report and stops. Suggested rewrites are proposals inside the report, never disk writes. To apply, hand off to content:editor.

Instructions

Content-type detection

Read the input. Match against these signatures. If signal is ambiguous, ask the user once before scoring.

Cross-cutting skills always loaded: content-voice, content-humanize, content-grounding.

Don't guess between blog and article — confirm if borderline. Don't guess platform if no cue — ask which one.

This audit covers the writing itself: hook, dwell, slop, voice, specificity, structure, grounding, safety, topic fit, and answer-first structure for long-form.

Inputs the audit accepts

Required: the content (file path or pasted text).

Optional context that sharpens the score (ask for missing items on a thorough audit, otherwise mark the axis "Unscored"): target platform, niche, account stage, audience, primary keyword, anchor accounts, brand voice notes (check memory first), posting time.

Score axes

Every audit returns the same axis set. Weight per axis varies by content type — see the weight table below. Score each 0–10 (10 = nothing to fix, 0 = blocking issue). Missing context = "Unscored — needs {context}".

Axis weights by content type

Normalise the per-axis 0–10 scores using these weights to get the 0–100 overall.

Weights sum to 100. Any axis flagged "Unscored" is dropped and the remainder re-normalised; report the dropped weight as "{N} pts unscored" so the reader sees coverage.

Phoenix-style verdict (X surfaces only)

After scoring, map the X audit to one of four verdicts. This is the harness's predicted reach posture — not a real Phoenix prediction, but a structured projection based on the algorithm mechanisms encoded in social-x.

For non-X content, omit the verdict and use the overall score band only: Strong (≥ 80) / Ship-ready (65–79) / Needs work (45–64) / Rewrite (< 45).

Severity matrix

Each finding gets a severity tier.

• Critical — blocks reach or ships a fabrication. Fix before publishing. (Kill-switch flag, fabricated stat, first-person experience with no author source, anonymous byline on YMYL, intent mismatch, information-gain-zero, missing hook.)
• Moderate — degrades performance noticeably. Fix when possible. (Slop-shape hook, dwell-risk wall of text, weak title/meta, missing answer-first block, voice drift.)
• Minor — polish. Optional. (One filler phrase, single data-free section, single passive sentence in an active piece.)

When the severity is ambiguous, default UP — flag as Critical and let the user decide to defer. Never silently downgrade safety findings.

Finding format

Every finding follows this shape so reports are diff-able and tools can parse them.

[SEVERITY] [AXIS] {one-line title}
  Where: {file:line OR section name OR "hook" / "post 2" / "conclusion"}
  Evidence: "{verbatim quote from the content, ≤ 25 words}"
  Why it matters: {one sentence tying to a specific algorithm or quality mechanism}
  Fix direction: {one sentence — what to change, not how to write it}
  Suggested rewrite: {optional — only when the fix is local and short; otherwise omit}

No suggested rewrites for structural findings (those are scoping decisions for the editor agent). No suggested rewrites for findings the auditor flagged as "needs verification" — preservation is the default.

Escalation rule

If a check cannot be completed, do not infer. Flag as "Unverified" with a precise reason:

• Missing input context (no niche given, no target keyword) → list as "Unscored axis — needs {context}; ask the user before re-scoring."
• Named entity the model has no training-data confidence on → "Unverified entity — would need {websearch / user source} before scoring grounding."
• Live signal needed (current SERP, current AIO presence) → "Unverified — needs live SERP fetch."
• Source content too short to evaluate an axis → "Unscored — not enough signal."

Never grade an axis from a guess. Unverified beats wrong.

Output report template

Save as in-conversation rendering by default. If user says "save it," write to content-audit-{slug}-{YYYY-MM-DD}.md in CWD. Never mutate the source file.

# Content Audit — {filename or "Pasted draft"}
 
Detected type: {X post / X thread / blog / article / ...}
Skills consulted: {social-x, content-voice, content-humanize, content-grounding, ...}
Context provided: {list}
Context missing (axes affected): {list, if any}
 
## Score
 
Overall: {N}/100 — {verdict band}
{Phoenix verdict line, X only}
 
| Axis | Score | Weight | Weighted |
|---|---|---|---|
| Hook | 7/10 | 20 | 14.0 |
| Dwell risk | 4/10 | 18 | 7.2 |
| ...
 
## Critical findings
 
[CRITICAL] [AXIS] {title}
  Where: ...
  Evidence: "..."
  Why it matters: ...
  Fix direction: ...
  Suggested rewrite: ...
 
## Moderate findings
...
 
## Minor findings
...
 
## What's working
 
- {strength 1}
- {strength 2}
 
## Recommended next step
 
{One of:}
- Ready to publish — minor polish optional.
- Run `content:editor` to apply the {N} critical and {N} moderate fixes.
- Rewrite recommended — structural issues; restart from a new outline.
- Get the missing context first ({list}) then re-audit.

Examples

Example — X single-post audit (abbreviated)

# Content Audit — pasted draft
 
Detected type: X post (single)
Skills consulted: social-x, content-voice, content-humanize, content-grounding
Context provided: niche=AI coding agents, account stage=mid (8k followers)
Context missing: none
 
## Score
 
Overall: 69/100 — Borderline
Phoenix verdict: Borderline — Dwell-risk axis at 4 is the choke point
 
| Axis | Score | Weight | Weighted |
|---|---|---|---|
| Hook | 8/10 | 20 | 16.0 |
| Dwell risk | 4/10 | 18 | 7.2 |
| Slop risk | 7/10 | 15 | 10.5 |
| Voice | 7/10 | 10 | 7.0 |
| Specificity | 6/10 | 10 | 6.0 |
| Structure | 5/10 | 5 | 2.5 |
| Grounding | 9/10 | 10 | 9.0 |
| Safety + brand-safety | 10/10 | 7 | 7.0 |
| Topic fit | 8/10 | 5 | 4.0 |
 
## Critical findings
 
[CRITICAL] [Dwell risk] Wall of text in first paragraph
  Where: post body, opening 3 lines
  Evidence: "Most teams don't realise that the actual problem with agents is not the model itself but rather..."
  Why it matters: First-screen non-dwell is a negative-weighted Phoenix signal; long unbroken text predicts scroll-past.
  Fix direction: Break the opening into 1-sentence-per-line; lead with the contrarian rule, not the setup.
 
## Moderate findings
...

Example — blog post audit (abbreviated structure)

Same report shape; Answer-first / GEO axis populated; Phoenix verdict line omitted; band verdict from overall score.

Checklist

Before returning a report:

• [ ] Content type detected explicitly and confirmed (or asked if ambiguous)
• [ ] All applicable platform + cross-cutting skills consulted (named in report header)
• [ ] Every axis has a score or an explicit "Unscored — needs {context}"
• [ ] Overall score uses the weight table for the detected type; un-scored weight re-normalised
• [ ] Phoenix verdict present for X; band verdict for everything else
• [ ] Every finding has severity, axis, where, evidence quote, why-it-matters, fix-direction
• [ ] Suggested rewrites only on local short fixes — not on structural findings
• [ ] Recommended next step routes to the right surface (publish / editor / outline / get-context)
• [ ] Report rendered in conversation; no source file mutated
• [ ] If saved, file path is content-audit-{slug}-{YYYY-MM-DD}.md in CWD

Composition / References

Content-domain skills the harness composes with:

• social-x, social-linkedin, social-threads, social-bluesky, social-mastodon, social-hackernews, social-reddit — platform rulebooks
• content-voice — voice / AI-pattern check
• content-humanize — 8-dimension humanization diagnostic (when Slop-risk score is low)
• content-grounding — fact-grounding triage for the Grounding axis
• content-geo — answer-first / extractable structure for the Answer-first / GEO axis