CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content-engine

Build and run an SEO content engine: audit current state, identify gaps, build keyword architecture, generate content calendar, draft content.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo/playbooks/seo-content-engine/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is concise, actionable, and well-structured as an orchestration playbook, with only workflow clarity held back by the absence of an explicit validation feedback loop for batch publishing. Adding a validate-before-publish loop would round it out.

Suggestions

Add an explicit validate→fix→retry step before publishing drafted content (e.g., review against brand voice and target keywords, fix gaps, re-check before publish) to satisfy the batch-operation feedback-loop guideline.

Make the post-publish monitoring loop concrete with named metrics and a fix-then-update retry path for underperforming pages.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence throughout — no concept explanations of SEO or content marketing; every line is actionable direction.

3 / 3

Actionability

Concrete, specific guidance throughout — named sub-skills per step, funnel-stage keyword templates, a week-numbered calendar, and a per-piece content checklist; absence of code is fine for this instruction-only skill.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced with human checkpoints, but there is no explicit validate→fix→retry feedback loop for the batch content-publishing operation, which caps workflow clarity per the batch-operations guideline.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized into clear sections (When to Use, Prerequisites, Steps, Cadence, Checkpoints) with no nested references.

3 / 3

Total

11

/

12

Passed

Description

60%

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 and action-oriented but omits any explicit trigger guidance, capping completeness and trigger quality. Adding a 'Use when...' clause with natural user phrasings would lift the lower dimensions.

Suggestions

Append a 'Use when...' clause naming natural trigger phrasings (e.g., 'Use when the user asks for an SEO content strategy, content calendar, keyword gaps, or what content to publish').

Replace technical phrasing like 'keyword architecture' and 'content engine' with terms users naturally say to improve trigger-term coverage.

Add an explicit when-to-use trigger to distinguish this skill from general content-creation or marketing skills.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'audit current state, identify gaps, build keyword architecture, generate content calendar, draft content' — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers 'what' but provides no explicit 'when'/trigger clause; per guideline a missing 'Use when...' caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain keywords (SEO, content calendar, keyword architecture) but leans technical and lacks coverage of natural variations a user would say, with no 'Use when...' phrasing.

2 / 3

Distinctiveness Conflict Risk

The 'SEO content engine' framing is a recognizable niche but lacks a distinct explicit trigger and could overlap with generic content/marketing skills.

2 / 3

Total

9

/

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
gooseworks-ai/goose-skills
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.