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

86%

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

75%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-sequenced, largely executable workflow with a complete output template and thoughtful embedded validation and untrusted-content rules. It is held back from the top band by inline time-sensitive facts, a handful of undefined external references (tier 1-3 sources, quality-scoring.md, orchestration-details.md), and a final confirmation step without explicit criteria.

Suggestions

Move dated facts (the 2026-05-07 FAQ rich-result retirement, the 2023 HowTo removal) and version markers like "v1.8.0" into a short 'Deprecated / old patterns' section, or drop the specific dates, to cut time-sensitive inline content (conciseness).

Define the "tier 1-3 sources" scheme inline in one line or link the file that defines it, and add `quality-scoring.md` and `orchestration-details.md` to the reference documents list so every external dependency is discoverable (actionability, progressive_disclosure).

Replace "Confirm the brief is ready for `/blog write`" with an explicit pre-save checklist, e.g. every statistics row has source + URL, every claimed gap traces to a competitor observation, and every template claim matches the recommended template file (workflow_clarity).

DimensionReasoningScore

Conciseness

The body is dense operational instruction with almost no concept explanations Claude doesn't need, but includes minor trimmable material: the framing line "Generates comprehensive content briefs that guide blog writing for maximum impact on both Google rankings and AI citation platforms", obvious template-table cells like "Step-by-step instructional content" for `how-to-guide`, and inline time-sensitive facts ("FAQ rich results were fully retired for all sites on 2026-05-07; HowTo rich results were removed in 2023", plus two "v1.8.0" version markers) that are not placed in a deprecated/old-patterns section.

4 / 5

Actionability

Guidance is overwhelmingly executable — an exact search string ("[topic] study <current year> data statistics research"), a complete copy-ready output template, and a concrete save path ("briefs/[slug]-brief.md") — but a few pointers dangle: "Prioritize tier 1-3 sources" (tier scheme undefined here), "the `quality-scoring.md` range" (file not in the reference list), and the `load_untrusted_root.py` helper "resolved as documented in the `blog` skill section" (external dependency). Not 5 because these leave small execution gaps; not 3 because nearly every step is fully specified without pseudocode.

4 / 5

Workflow Clarity

Steps 1→2→2.5→3→4→5→6 are clearly sequenced with numbered substeps and embedded checkpoints ("Drop unverifiable statistics instead of carrying them as weak claims", "mark surfaces as unavailable when not directly checked", "label estimates as snippet-only", "If the helper is missing or fails, skip the file" as an error-recovery path). Not 5 because the final step's check ("Confirm the brief is ready for `/blog write`") is a rubber stamp with no explicit criteria, e.g. no checklist that every statistics row has a source URL; not 3 because validation is explicit throughout, not merely implied.

4 / 5

Progressive Disclosure

The reference list is well-signaled with one-line purposes per file ("template selection criteria", "channel-specific distribution tactics", "link architecture patterns") and appears one level deep, with the 12-template table acting as an inline overview whose details live in `content-templates.md`. Not 5 because `orchestration-details.md` and `quality-scoring.md` are referenced only in prose/template placeholders rather than the reference list, and no local bundle files exist — all references resolve to a sibling skill's directories, so none can be verified from this bundle. Not 3 because structure is otherwise good and references are mostly clear.

4 / 5

Total

16

/

20

Passed

Description

92%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 excellent description that explicitly states what the skill produces with a comprehensive component list, gives four concrete quoted trigger phrases, and sharply disambiguates against four named sibling skills. The only soft spot is trigger coverage that stays within a single word family ('brief').

DimensionReasoningScore

Specificity

The description enumerates the full component set of the deliverable — "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" — eight concrete components with no real coverage gap, matching the comprehensive multiple-actions anchor. Not 4 because coverage of what a brief contains is complete rather than having minor gaps.

5 / 5

Completeness

Both halves are explicit: the what ("Create a content brief for ONE planned post: target and secondary keywords, ... distribution ideas") and the when with concrete trigger phrases ("Use when the user says 'content brief', 'blog brief', 'SEO brief', 'article brief'"). Not 4 because the when-clause is fully explicit with quoted triggers rather than merely present-but-imprecise.

5 / 5

Trigger Term Quality

Four natural quoted trigger phrases — "content brief", "blog brief", "SEO brief", "article brief" — give good keyword coverage a user would plausibly say. Not 5 because all variants come from one word family ("brief") and other natural phrasings (e.g. "brief for a post", "keyword brief") are absent; not 3 because four natural quoted triggers exceeds 'some relevant keywords with missing variations'.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and actively prevents mis-triggering with explicit negative boundaries: "Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write)". Not 4 because overlap risk is not just minor but explicitly addressed against named sibling skills.

5 / 5

Total

19

/

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.