CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-coach

Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/seo-coach/SKILL.md

The canonical home for this skill is seo-coach in every-app/open-seo

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-structured, instruction-only coaching skill that is highly actionable — exact tool names, literal write-back payloads, explicit handoff triggers, and complete example dialogues — with no padded explanations. Its only real weaknesses are mild duplication between the workflow listing sections and the absence of any offloading into reference files.

DimensionReasoningScore

Conciseness

Nearly every line carries project-specific knowledge Claude cannot know (the workflow catalog, MCP tool inventory, GSC and handoff rules), with no basic-SEO padding. It misses 5 because "Suggested next actions" largely repeats "What each workflow does" and the two example replies could be tightened; it is well above 3 since nothing is genuinely unnecessary.

4 / 5

Actionability

Guidance is fully concrete and ready to use: exact tool names (`get_project_context`, `update_project_context`, `get_search_console_performance`, `list_reports`), the literal write-back payload `{ appendResearchLog: { summary: "..." } }`, explicit handoff triggers ("when the user asks for a report, a full analysis, 'everything about'"), invocation forms (`/openseo:<skill>` vs `/<skill>`), and two complete example replies covering the common cases. For an instruction-only skill this matches the top anchor.

5 / 5

Workflow Clarity

"Project context" is a numbered sequence with explicit checkpoints (resolve the project with `list_projects` if needed, check the research log before spending credits, let `missingSections` shape the recommendation) and the coaching patterns are clearly sequenced. It misses 5 because there is no error-recovery guidance for failed tool calls or stale context, and sits above 3 because checkpoints are explicit rather than implicit; no destructive or batch operations apply to cap it.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with clear section headers, no buried or nested references, and every section serves the coach role. The 5-score exception is limited to skills under 50 lines; this ~160-line body inlines the full workflow catalog and tool-coaching inventory that could arguably live in one-level-deep reference files, placing it at 'good structure; most content appropriately placed'.

4 / 5

Total

17

/

20

Passed

Description

66%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 with several concrete, third-person actions and mostly natural trigger terms. Its main weakness is the complete absence of a 'when to use this' clause, which caps completeness and leaves triggering to inference.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks what to do next with their SEO, wants a workflow explained, or is unsure where to start with OpenSEO."

Include plain "SEO" and "explain" as natural keywords so the description triggers even when the user never says the brand name "OpenSEO".

Sharpen the generic tail "helps users use agents, web search, scraping, and MCP data effectively" into concrete actions like "explains when to use MCP data vs. web search vs. page scraping".

DimensionReasoningScore

Specificity

Lists several concrete actions — "explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data" — which matches the 'several specific actions; minor gaps' anchor rather than the 3 anchor's 1-2 actions. It falls short of 5 because "helps users use ... effectively" is generic rather than a concrete action; voice is third person, so no pronoun penalty applies.

4 / 5

Completeness

The 'what' is clear (a coach mode that explains workflows and recommends next steps), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot be 4 because the 'when' is entirely absent, not merely implicit or imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "coach", "workflows", "next steps", "web search", "scraping", "MCP". Coverage is better than the 3 anchor's 'some relevant keywords', but not 5 because common variations are missing — notably plain "SEO" (only inside the brand "OpenSEO") and terms like "explain" or "beginner".

4 / 5

Distinctiveness Conflict Risk

The description carves a distinct niche anchored to the OpenSEO brand ("Enter a friendly OpenSEO coach mode"), but the closing clause "helps users use agents, web search, scraping, and MCP data effectively" is broad enough to overlap with the workflow skills it describes and general agent-guidance skills. This fits 'mostly distinct; minor overlap risk' rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

every-app/open-seo

Path

.agents/skills/seo-coach/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.