content-review

name	content-review
description	Final quality gate for a brand-new Career Hub draft. Use only at the end of the new-content pipeline to score an unpublished article before it is accepted.
metadata	{"family":"content","owner":"content","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"}

Content Review

Score the new draft before it is accepted for implementation.

Boundary

• Use this skill only for brand-new unpublished content.
• Do not use it for site audits, CRO reviews, SEO diagnostics, or code review.

Editorial Standard

Read nextjs-app/docs/BRAND.md for editorial thresholds, banned phrases, and quality criteria.

What To Review

Score the draft across:

1. usefulness
2. brand tone
3. data accuracy
4. SEO value
5. AEO readiness
6. implementation readiness

Implementation Readiness

Content review is the final editorial acceptance gate. It should decide whether the content is strong enough to hand to the code family, not implement or verify the route.

Check:

• Is the page genuinely useful to the target worker?
• Is the draft specific enough to avoid generic AI writing?
• Are the key claims traceable to credible sources?
• Is the page aligned with brand tone and search intent?
• Is it strong enough to justify code-family implementation?
• Does the handoff list route-level requirements such as pnpm audit:responsive, metadata, schema, and internal links when those are needed?

Review Inputs

• edited draft
• Research Dossier
• Content Plan

Output

Return:

• pass or fail
• dimension scores
• critical blockers
• concrete fix list
• final recommendation
• structured implementation handoff requirements, if accepted

When accepted, include this block:

implementation_handoff:
  requires_code_family: true
  target_destination: "<feature-owned data or route path>"
  required_code_skills:
    - data-placement
    - verification-checklist
  route_requirements:
    - metadata
    - schema
    - internal_links
  verification_required:
    - pnpm audit:responsive

Use only requirements that apply to the accepted draft. Keep pnpm audit:responsive as code-family verification, not a content-review action.

Review Discipline

• Validate claims against the dossier.
• Check the draft shape against the destination TypeScript type.
• Flag thin sections, weak examples, and unsupported claims.
• Prefer specific edit instructions over generic feedback.
• Do not perform code-family route wiring, browser verification, or pnpm audit:responsive from this skill.