CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog

Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.

Quality

89%

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

85%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-engineered orchestrator body: concrete executable commands, a validation-gated delivery workflow with explicit retry caps, and clean one-level-deep on-demand references that all resolve to real files. The main cost is token weight — an inline ~95-line security contract with rationale prose, a duplicated routing table, and scattered version/date annotations make it longer than the task requires.

Suggestions

Move the explanatory prose of the Untrusted-Data Contract (the 'Why the nonce' paragraph, outer-nonce authority explanation, and defense-class summary table) into a reference file, keeping only the mandatory invocation steps and rules inline in SKILL.md.

Merge the Quick Reference table and the Command Routing list into one table with an alias column, eliminating the duplicated command-to-sub-skill mapping.

Strip changelog-style version and date annotations (v1.8.0, v1.8.3, v1.9.0, 'updated 2026-10-05', 'May 2026 Core Update') from operational sections, or consolidate them into a single changelog/deprecated section in a reference file.

DimensionReasoningScore

Conciseness

Most of the body is tight operational content (routing tables, gate thresholds, bash blocks), but it could be tightened: the ~95-line inline Untrusted-Data Contract includes rationale prose ("Why the nonce: an attacker who controls the file contents cannot pre-embed..." plus a defense-class summary table), the Command Routing section largely restates the Quick Reference table, and changelog-style version/date annotations ("(v1.8.0)", "(v1.9.0)", "updated 2026-10-05", "May 2026 Core Update") add tokens without operational value. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably padded profile of a 2, since nearly all inline material is instructions Claude must follow rather than concepts it already knows.

3 / 5

Actionability

The execution flow gives copy-paste-ready commands with real flags and arguments ("python3 "$BLOG_SCRIPT_DIR/blog_preflight.py" --draft "$D" --gate 1", "generate_hero.py --topic '<title>' --tags '<tags>' --out "$D"", "NONCE=$(python3 ... --init-review-nonce --draft "$D")"), a concrete alias routing map, and explicit platform-detection signals. Variables are defined ("Draft folder `D`, slug `S`") and placeholders are governed by the stated shell-quoting rule, so the common cases are fully covered.

5 / 5

Workflow Clarity

The /blog write flow has an explicit ordered sequence with validation checkpoints and feedback loops: create the draft folder, "run Gate 1 before writing", re-render and re-init the nonce after any change, "at most 3 failed full gate runs per draft... then stop and present the diagnostic, not the draft", and deliver only when all gates pass. This matches the top anchor (clear sequence, explicit validation, error-recovery loops); a 4 would require missing checkpoints, but gates, caps, and retry semantics are all stated.

5 / 5

Progressive Disclosure

The body is an overview-plus-routing document backed by 22 reference files that all exist in the bundle's references/ directory, each listed with a one-line description under "Load on-demand as needed... load only what the task needs", and references are one level deep (e.g., quality-scoring.md is named as the single source for scoring thresholds, orchestration-details.md for agent roles). Scoring against the actual bundle structure, navigation is easy and content is appropriately split; the minor duplication of the routing table is not enough to drop to the 'minor organization gaps' anchor.

5 / 5

Total

18

/

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.

A strong description that clearly states what the skill does, when to use it, and when not to, with concrete capability enumeration and explicit negative trigger guidance. The only weakness is that a handful of natural trigger phrases (write, edit, SEO audit) are absent from the 'Use when' clause even though they appear as capabilities.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — "writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing" — which is comprehensive coverage of the skill's actions rather than vague domain language. It matches the anchor for multiple specific concrete actions; a 4 would require minor gaps in coverage, but the capability list plus "100-point scoring" and "5 agents" spans the full surface.

5 / 5

Completeness

It explicitly answers both questions: what ("Full-lifecycle blog engine with 31 sub-skills... Routes requests to the right sub-skill") and when ("Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand"), with concrete trigger phrases. This matches the top anchor exactly; a 4 would require the 'when' clause to be less explicit.

5 / 5

Trigger Term Quality

Trigger terms are natural verbs users would say — "create, revise, analyze, plan, translate, localize, audit, or repurpose blog content" — plus direct invocation via "/blog subcommand". A few natural phrases are still missing (e.g., "write a blog post", "edit", "SEO audit"), which fits the anchor of good keyword coverage with a few natural terms missing rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (blog content lifecycle) and actively reduces false triggers: "Do not activate merely because the word 'blog' appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request." Distinct triggers plus explicit exclusion guidance put it at the minimal-conflict-risk anchor; a 4 would need minor overlap risk with closely related skills, which the negative trigger clause addresses.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

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