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.

61

Quality

72%

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

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

The body is a well-structured orchestration playbook with a clear sequenced workflow and explicit human validation checkpoints; it is concise and actionable, with only minor opportunities to tighten restated framing.

DimensionReasoningScore

Conciseness

Mostly lean bullet-driven content with no padding or re-explained concepts; only minor restatement of the audit→publishing pipeline already given in the description.

4 / 5

Actionability

Names concrete sub-skills (seo-content-audit, aeo-visibility, content-asset-creator) and specific frameworks (funnel stages, keyword clusters, week-by-week calendar); as an orchestration playbook it appropriately delegates execution, with minor gaps.

4 / 5

Workflow Clarity

Clear 7-step sequence with an explicit Human Checkpoints section providing validation gates after steps 2, 4, and 5, plus an ongoing cadence — well-sequenced with feedback loops.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references; no bundle files exist so all content is inline, which is appropriate for this length but leaves minor room to split detail out.

4 / 5

Total

17

/

20

Passed

Description

63%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 is specific and distinct, naming five concrete engine-building actions, but omits any explicit 'Use when' trigger guidance, which limits completeness and natural trigger-term coverage.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks for an SEO content strategy, content calendar, or keyword architecture for a client').

Include natural user-facing synonyms such as 'content strategy', 'SEO plan', or 'keyword research' alongside 'SEO content engine'.

Clarify the client-deliverable framing so the trigger is distinguishable from generic content-drafting skills.

DimensionReasoningScore

Specificity

Lists five concrete actions — 'audit current state, identify gaps, build keyword architecture, generate content calendar, draft content' — giving comprehensive coverage of the domain.

5 / 5

Completeness

The 'what' is clearly stated via the five actions, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant phrases ('SEO content engine', 'content calendar', 'draft content') but misses common user variations like 'content strategy' and any synonyms or file extensions.

3 / 5

Distinctiveness Conflict Risk

'SEO content engine' carves a clear niche with minor overlap risk against generic content/marketing skills; mostly distinct.

4 / 5

Total

15

/

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.