CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is content-brief-authoring in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured, opinionated skill with a clear overview-to-references split, concrete field-level guidance, and a workable authoring/audit framework. Its main cost is token redundancy: a near-duplicate restatement of the 12 fields and repeated thesis lines could be cut with no loss of instruction.

Suggestions

Collapse 'The framework: 12 considerations for brief authoring' — it restates the '12 fields of an effective brief' section item for item; keep one formulation and reference it.

Cut the four-intent taxonomy bullets (informational/navigational/commercial/transactional) down to one line and keep only the brief-specific value-add: the dominant SERP format check and the SERP-override pattern.

Remove the duplicated 'Most briefs that are not working are thin, not thick' thesis (appears in 'Thin vs thick vs effective briefs' and again in the closing) and merge the closing checklist into the framework section.

DimensionReasoningScore

Conciseness

Mostly efficient and opinionated, but padded in places: 'The framework: 12 considerations' restates the earlier '12 fields' section almost item for item, 'Most briefs that are not working are thin, not thick' appears nearly verbatim twice, and the four-intent taxonomy (informational/navigational/commercial/transactional) is knowledge Claude already has. Not 4: these are not merely minor trimmable instances — a whole redundant section and a duplicated thesis statement.

3 / 5

Actionability

Concrete, executable guidance throughout: a 12-field checklist with specific counts ('3 to 5 supporting keywords', '3 to 5 pages this piece should link out to', 'a 40 to 60 word answer paragraph'), a 4-step entity-discovery procedure, and a closing ship/no-ship checklist. Not 5: there is no inline populated example brief — the worked examples all live behind references, so the common case is covered indirectly.

4 / 5

Workflow Clarity

Sequences are clear and checkpointed: the entity-discovery pattern is numbered, the brief-to-writer handoff is ordered with explicit review framing, governance defines versioning and approval flow, and the closing checklist validates readiness ('are all 12 fields populated... is the document under 2 pages?'). Not 5: validation is implicit in some flows (e.g., SERP-format check and self-cannibalization check are described but not wired into an ordered validation sequence with error-recovery loops).

4 / 5

Progressive Disclosure

The body is a clear overview with one-level-deep, well-signaled references: every detail section ends with 'Detail in references/...', and a Reference files section lists all 8 files with one-line descriptions. All 8 referenced files exist in the bundle; no nesting or buried references. Not 4: organization and navigation leave nothing to improve at this scope.

5 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

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

A strong description: it names the niche precisely, enumerates the brief's fields comprehensively, states an explicit trigger list with natural phrasings, and positions the skill against thin and thick alternatives. The only weakness is mild trigger overlap with closely related sister skills.

DimensionReasoningScore

Specificity

The description enumerates the skill's concrete deliverables comprehensively: 'target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria', plus positioning ('The middle path between thin briefs... and thick briefs'). Not 4: coverage of what the skill produces is complete with no material gaps, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Both what and when are explicit: what — 'How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both'; when — 'Triggers on...' and 'Also triggers when briefing a human writer or an AI agent on a single content piece'. Matches the anchor with concrete trigger phrases; not 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with natural phrasings and synonyms: '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', plus 'briefing a human writer or an AI agent on a single content piece'. Not 4: no common natural variation is missing.

5 / 5

Distinctiveness Conflict Risk

Scoped to the per-piece brief niche ('Per-piece editorial brief', 'The middle path between thin briefs... and thick briefs'), which distinguishes it from program-level and writing skills. Not 5: broad trigger phrases like 'brief the writer' and 'brief audit' carry some overlap risk with closely related skills such as creative-brief or content-strategy.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/content-brief-authoring/SKILL.md

Reviewed

Table of Contents

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.