content-brief-authoring

How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief, target keyword brief, search intent brief. Also triggers when briefing a human writer or an AI agent on a single content piece.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, opinionated, and actionable with strong progressive disclosure to real reference files. Its main weakness is repetition: the 12-field list and thin/thick framing each appear twice.

Suggestions

Collapse the 'framework: 12 considerations' section into a pointer back to 'The 12 fields of an effective brief' rather than restating the list, or vice versa, to remove the duplicated enumeration.

Trim the Closing section, which restates the thin-vs-thick distinction already covered in 'Thin vs thick vs effective briefs'; a one-line contract restatement would suffice.

Consider moving the per-content-type field-weight table fully into references/brief-templates.md and keeping only a one-line pointer in the body to tighten the overview further.

Dimension	Reasoning	Score
Conciseness	Prose is mostly efficient and assumes Claude's competence (no basic-concept padding), but the 12 fields are restated as a second '12 considerations' framework and the thin/thick distinction is repeated in the closing, so not every token earns its place.	2 / 3
Actionability	Concrete, specific guidance throughout — entity discovery as a numbered 4-step process, '3 to 5 outbound links... 1 to 3 inbound', intent override pattern, and per-type field-weight notes — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	The 12-consideration framework provides a clear sequenced walkthrough and the closing readiness checklist ('ask: are all 12 fields populated... If yes to all, ship the brief') acts as an explicit validation checkpoint, with common-failure-modes serving as error-recovery reference.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references — each section ends with 'Detail in [references/...]' and a consolidated Reference files section lists all 8 bundles, all of which exist on disk.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and explicitly signals both capability and activation conditions in third person. It cleanly distinguishes the per-piece brief discipline from adjacent skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete brief components — 'target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers what ('How to author a content brief that actually guides a writer...') and when via an explicit 'Triggers on...' clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Explicit 'Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief...' plus an 'Also triggers when briefing a human writer or an AI agent' clause gives broad coverage of natural phrasings a user would say.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche — the per-piece editorial brief 'between thin briefs... and thick briefs' — with distinct triggers unlikely to fire for project- or program-level briefing skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.