CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-brief

Create a content brief for ONE planned post: target and secondary keywords, search intent, template choice, competitor gaps from the live SERP, sourced statistics to include, section plan, internal-link targets, and distribution ideas. Use when the user says "content brief", "blog brief", "SEO brief", "article brief". Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write).

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, highly actionable workflow skill: every step carries concrete parameters and a complete output specification, with well-signaled external references. Remaining improvement is structural — move the large inline output template to a reference file, add a pre-save validation checkpoint, and trim the small duplications.

Suggestions

Move the full brief output template (the ~160-line fenced block in Step 5) into a reference file such as references/brief-output-template.md and keep a compact field checklist inline in SKILL.md.

Add an explicit validation checkpoint between Step 5 and Step 6: verify every brief section is present, every statistic carries provenance, and internal-link targets exist before saving.

Trim the 12-row template table to a name-only list (or defer it entirely), since selection criteria already live in content-templates.md — this removes duplication and tightens conciseness.

DimensionReasoningScore

Conciseness

The body is lean, assumes competence, and explains no basic concepts; nearly all prose is directive. Minor trim candidates keep it below the top anchor: the marketing-flavored line "Generates comprehensive content briefs that guide blog writing for maximum impact on both Google rankings and AI citation platforms", and the 12-row template table whose selection criteria are already delegated to content-templates.md. It sits above anchor 3 because there is no genuinely unnecessary explanation — only small duplication.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: concrete search strings ("[topic] study 2025 2026 data statistics research"), numeric parameters throughout (3-5 secondary keywords, top 3-5 pages, ~8-12 stat pool, 6-8 H2 sections), a complete fill-in output template, and an explicit save path ("briefs/[slug]-brief.md" with directory creation). No gaps remain between high-level direction and executable steps.

5 / 5

Workflow Clarity

The six-step sequence (Intake, Keyword Research, Template Recommendation, Competitive Analysis, Statistics Research, Generate, Save) is clearly ordered with defined substeps, and Step 4 embeds verification (record provenance, "Drop unverifiable statistics"). It falls short of anchor 5 because there is no explicit validation checkpoint after Step 5 (e.g., verifying the generated brief covers all sections and every stat has provenance before saving); it is not anchor 3 since checkpoints like source-dropping and URL validation are present.

4 / 5

Progressive Disclosure

References are well signaled: a "Reference documents:" list names five sibling files each with a one-line purpose ("template selection criteria", "channel-specific distribution tactics"), one level deep, plus template files under templates/[type].md. The top anchor is missed because the ~160-line brief output template and the 12-template table are inlined in SKILL.md rather than split into a reference file, making the body less of a pure overview.

4 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: it states a concrete, comprehensive set of deliverables, provides explicit natural trigger phrases, and closes with explicit negative boundaries against sibling skills. Both "what" and "when" are answered clearly and distinctly.

DimensionReasoningScore

Specificity

The description enumerates eight concrete deliverables — "target and secondary keywords", "search intent", "template choice", "competitor gaps from the live SERP", "sourced statistics to include", "section plan", "internal-link targets", and "distribution ideas" — giving comprehensive, non-generic coverage of what the brief contains. Anchor 4 ("minor gaps in coverage") does not apply since every major brief component is named.

5 / 5

Completeness

It explicitly answers both "what" ("Create a content brief for ONE planned post" with enumerated components) and "when" ("Use when the user says 'content brief', 'blog brief', 'SEO brief', 'article brief'") with concrete trigger phrases. This mirrors the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say — "content brief", "blog brief", "SEO brief", "article brief" — covering the synonym space for this task type. No file extensions are relevant here, so coverage matches the top anchor.

5 / 5

Distinctiveness Conflict Risk

The negative boundary clause — "Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write)" — explicitly disambiguates four sibling skills, giving a clear niche with minimal conflict risk.

5 / 5

Total

20

/

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

AgriciDaniel/claude-blog

Path

skills/blog-brief/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.