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

84%

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

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 strong progressive disclosure and concrete, numbered guidance throughout. Its main weaknesses are internal redundancy (the 12 fields appear twice, the thin-vs-thick framing appears three times) and the absence of a single worked example brief inline.

Suggestions

Cut 'The framework: 12 considerations' section, which restates the 12 fields section nearly item-for-item, or merge it into the 12-fields section as a compact recap checklist; likewise remove the verbatim repetition of 'Most briefs that are not working are thin, not thick' from the Closing.

Compress the four-intent taxonomy in 'Search intent classification' (Informational/Navigational/Commercial/Transactional definitions are standard SEO knowledge) down to the SERP-format check and the override pattern, which are the skill's non-obvious contributions.

Include one condensed worked example brief (or a filled-in excerpt of the pillar template) inline in the body so a strategist can see the target artifact shape without opening references/brief-templates.md.

DimensionReasoningScore

Conciseness

The body is mostly dense and opinionated, but has real duplication: 'The framework: 12 considerations' restates 'The 12 fields of an effective brief' almost item-for-item, and 'Most briefs that are not working are thin, not thick' appears verbatim in both the 'Thin vs thick' section and the Closing. The four-intent taxonomy ('Informational. The reader wants to learn...') also re-explains standard SEO knowledge Claude already has.

3 / 5

Actionability

Guidance is concrete throughout — '3 to 5 supporting keywords', 'a 40 to 60 word answer paragraph immediately following an H2 question', '3 to 5 pages this piece should link out to... 1 to 3 existing pages' — plus a numbered 4-step entity discovery procedure and failure modes with fixes. The gap is that no complete worked example brief appears in the body; templates are deferred to references/brief-templates.md.

4 / 5

Workflow Clarity

Checkpoints are present: the 12-consideration framework acts as an authoring checklist and the closing ship-check ('are all 12 fields populated... If yes to all of those, ship the brief') is an explicit validation gate, with failure modes paired to fixes. However, the end-to-end authoring workflow is scattered across topical sections rather than presented as one coherent ordered sequence with validation after each stage.

4 / 5

Progressive Disclosure

Each section closes with 'Detail in [`references/...`]' and a consolidated 'Reference files' section lists all eight files with descriptions; all eight referenced files exist in the bundle and are one level deep (reference files cross-link siblings only). Overview content is appropriately split from detail.

5 / 5

Total

16

/

20

Passed

Description

91%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 with explicit what/when structure, comprehensive natural trigger terms, and a clearly scoped per-piece editorial niche. Its only weaknesses are the action coverage limited to authoring and minor trigger overlap with adjacent brief-family skills.

DimensionReasoningScore

Specificity

The description enumerates concrete brief components — 'target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria' — which is several specific items with comprehensive field coverage. It falls short of a 5 because the stated action is limited to authoring; auditing existing briefs and building templates (capabilities the body claims) are not stated.

4 / 5

Completeness

It clearly answers both what ('How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both') and when, with concrete trigger phrases ('Triggers on... brief audit, per-piece brief, editorial brief...'). Both halves are explicit and specific.

5 / 5

Trigger Term Quality

It lists ten explicit natural trigger phrases — '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' — covering synonyms and natural phrasings users would actually say, plus a natural-language clause ('Also triggers when briefing a human writer or an AI agent on a single content piece').

5 / 5

Distinctiveness Conflict Risk

'Per-piece editorial brief' and 'a single content piece' pin a clear niche with mostly distinct triggers ('target keyword brief', 'search intent brief' are unambiguously SEO-content). Minor overlap risk remains with closely related brief/strategy skills via unqualified phrases like 'brief authoring' and 'brief audit', which is anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

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.