CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-brief

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citation visibility as part of SEO. Use when user says "content brief", "blog brief", "write brief", "SEO brief", "article brief", or "content requirements".

72

Quality

88%

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

77%

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

The body is a well-sequenced, actionable instruction skill with explicit quality-gate checkpoints, but it is padded by a large inline output template and its key reference/template files are absent from the bundle, weakening progressive disclosure and conciseness.

Suggestions

Move the ~160-line brief output template into a separate references file (e.g. references/brief-template.md) and link to it, keeping only a short schema sketch inline to tighten conciseness and improve progressive disclosure.

Either include the referenced files (skills/blog/references/*.md, skills/blog/templates/[type].md) in the bundle or correct the paths so signaled references resolve to real files.

Add an explicit validation/review checkpoint in Step 6 (e.g. verify all statistics have provenance and all cited URLs resolve) before saving the brief, to strengthen the workflow feedback loop around the final artifact.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the ~160-line inline brief output template and the full 12-template table are substantial inline content that pads the file; it is not level-1 verbose (no basic-concept explanations) but not the lean level-3 either.

2 / 3

Actionability

Guidance is concrete and executable for an instruction-only skill: numbered steps, exact search-query templates, a fully specified output schema, explicit safe-WebFetch rules, and provenance requirements — copy-ready rather than abstract.

3 / 3

Workflow Clarity

A clear six-step sequence is given with explicit quality gates/checkpoints — 'mark surfaces as unavailable when not directly checked', 'Drop unverifiable statistics', 'validate source URLs before citing', label snippet-only estimates — providing feedback loops for the fragile research operations.

3 / 3

Progressive Disclosure

References are signaled and conceptually one level deep, but the referenced paths (skills/blog/references/*.md and skills/blog/templates/*.md) do not exist in the bundle, and the large inline brief template is content that could be split out — structure is present but not cleanly realized at level 3.

2 / 3

Total

10

/

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, third-person, and clearly states both capabilities and explicit use-when triggers, hitting the top anchor on every dimension. Voice is correctly third person ('Generate...') with no first/second-person penalty.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — 'target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts' — matching the multi-specific-action anchor rather than the domain-only level 2.

3 / 3

Completeness

It explicitly answers both what (the enumerated brief components) and when (the 'Use when user says...' clause), satisfying the explicit-trigger anchor for the top level.

3 / 3

Trigger Term Quality

It lists natural phrases a user would say — "content brief", "blog brief", "write brief", "SEO brief", "article brief", or "content requirements" — giving broad, natural coverage rather than just one keyword.

3 / 3

Distinctiveness Conflict Risk

The SEO/AI-citation blog-brief niche is specific and paired with distinct trigger phrases, making confusion with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.