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.

57

Quality

66%

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

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 lean, well-structured orchestrator playbook: concrete keyword templates, a prioritization formula, a sequenced calendar, and explicit human review checkpoints. Its main weaknesses are the absence of error-recovery feedback loops around the checkpoints and the lack of invocation details or paths for the delegated sub-skills.

Suggestions

Add a recovery step to each Human Checkpoint, e.g. 'If the client rejects the calendar, revise priorities and re-review before drafting', to close the workflow feedback-loop gap.

Give each delegated sub-skill a concrete invocation hint (skill path or expected inputs/outputs) so the orchestration is executable without guessing, e.g. 'seo-content-audit: run site-content-catalog first, then feed the inventory into seo-domain-analyzer'.

DimensionReasoningScore

Conciseness

Terse bullet style that assumes SEO competence — it never explains what domain authority, TOFU/MOFU/BOFU, or programmatic SEO are — and every section carries load-bearing instructions. A few summary sentences ('Complete picture of where the client stands in search') could be trimmed, so anchor 4 fits better than the fully lean anchor 5.

4 / 5

Actionability

As an instruction-only orchestrator it gives concrete guidance: named sub-skills to invoke (seo-content-audit, aeo-visibility, content-asset-creator), literal keyword templates ('[Company] vs [Competitor]', 'how to choose [solution]'), a prioritization formula (volume x intent x difficulty), and a week-by-week calendar. Minor gaps remain — no invocation details, inputs, or expected outputs for the delegated sub-skills — so it falls short of fully executable anchor 5.

4 / 5

Workflow Clarity

A clear 7-step numbered sequence with explicit Human Checkpoints after Steps 2, 4, and 5, plus an ongoing monitor/review cadence. However, there is no guidance for what to do when a checkpoint review rejects the output and no error-recovery feedback loop, which anchor 5 requires.

4 / 5

Progressive Disclosure

The body is well organized into scannable sections and stays at overview altitude rather than inlining deep reference material, with no bundle files to misplace. The named sub-skills are given without paths or links, leaving a minor navigation gap versus the clearly signaled references of anchor 5.

4 / 5

Total

16

/

20

Passed

Description

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

The description clearly states what the skill does through five enumerated pipeline actions, but it entirely lacks a 'Use when...' trigger clause, capping completeness at 3 and weakening trigger-term quality. Natural user phrasings like 'SEO strategy' or 'keyword research' are absent, though the domain niche itself is well-distinguished.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for an SEO or content strategy, keyword research, a content calendar, or wants to know what content a company should publish.'

Add natural synonym phrasings users would actually say — 'SEO strategy', 'content strategy', 'keyword research', 'rank higher in search' — alongside the current domain terms.

Make the two generic actions concrete: replace 'audit current state' with 'audit content inventory, domain authority, and keyword rankings' and 'identify gaps' with 'identify competitive, funnel, and topic content gaps'.

DimensionReasoningScore

Specificity

Lists five named actions ('audit current state, identify gaps, build keyword architecture, generate content calendar, draft content'), but 'audit current state' and 'identify gaps' are semi-generic and later pipeline stages (internal linking, publishing, monitoring) are omitted. Several specific actions with minor coverage gaps matches anchor 4, not the comprehensive coverage of anchor 5.

4 / 5

Completeness

The 'what' is clear — build and run an SEO content engine with five enumerated actions — but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('SEO', 'content calendar', 'keyword architecture') but misses natural variations users would actually say, such as 'content strategy', 'SEO strategy', 'keyword research', or 'rank higher'. This is 'some relevant keywords but missing common variations', not the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

'Build and run an SEO content engine' with SEO-specific vocabulary carves a clear niche with minimal conflict risk; only minor overlap with generic content-marketing skills. Mostly distinct rather than a fully unique trigger profile, so anchor 4 fits better than 5.

4 / 5

Total

14

/

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.

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.