CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-project-setup

Populate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake.

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-project-setup/SKILL.md

The canonical home for this skill is seo-project-setup 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.

The body is a strong, well-structured workflow: concrete tool contracts, explicit failure paths, guardrails against overwriting context, and a clear output format make it highly actionable. Its only notable gaps are minor conciseness trim points and the lack of a post-write verification checkpoint. As a self-contained single-file skill it needs no bundle files and navigates cleanly.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout (no explanations of what SEO or Search Console are) with tight, purposeful sections, but the "Tone" section and the long goal-bullet enumeration in step 4 are minor instances of over-explanation that could be trimmed — fitting the 'efficient; minor instances' anchor rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact MCP tool signatures, copy-paste-ready patch-op shapes, concrete file names (gsc/queries-last-3-months.csv), a folder structure, example competitor notes ("direct competitor, owns the comparison pages"), example measurable goals, and a next-workflow decision table — matching the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

A clear 10-step sequence with error-recovery branches (ambiguous project → ask; none → create_project; MCP unavailable → tell the user), a read-before-write step, and guards like verifying Search Console via get_search_console_performance fits 'clear sequence with most checkpoints present'; not 5 because there is no post-write verification step (e.g. re-reading project context after update_project_context to confirm the patch landed).

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files and no nested references, the content is a cohesive interview flow that appropriately lives inline with well-signaled sections; minor gaps (the next-workflow map and GSC export details could be split into references if the skill grows) place it at 'good structure; most content appropriately placed' rather than fully optimal.

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 is specific and domain-distinct, clearly stating what the skill populates and naming natural terms like Search Console, competitors, and positioning. Its main weakness is the complete absence of any 'when to use' trigger clause, which caps completeness and slightly raises conflict risk with sibling OpenSEO skills. It is also missing the plain keyword "SEO" outside the product name "OpenSEO".

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up a new SEO project in OpenSEO, onboarding a site, or when project context is missing or incomplete."

Include the standalone natural term "SEO" (not only "OpenSEO") so users saying "set up SEO for my site" surface the skill.

Name the primary actions with verbs (e.g. "interview the user", "connect Search Console", "save competitors") instead of the single verb "Populate".

DimensionReasoningScore

Specificity

"Populate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake" lists several concrete intake areas and two concrete operations, matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because 'populate' is the only strong verb and action coverage is not comprehensive.

4 / 5

Completeness

The 'what' is clear and enumerated (populate context with site scope, goals, positioning, competitors, key pages, preferences, plus MCP checks and Search Console intake), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; not 2 because the 'what' is explicit and detailed rather than vague.

3 / 5

Trigger Term Quality

Natural domain terms users would say are present ("Search Console", "competitors", "goals", "positioning", "key pages"), fitting 'good keyword coverage; a few natural terms missing'; not 5 because the standalone term "SEO" never appears (only the product name "OpenSEO") and no setup-oriented phrases like "new site" are included.

4 / 5

Distinctiveness Conflict Risk

"Populate a project's shared OpenSEO context" carves a distinct niche (context intake rather than audits or research), fitting 'mostly distinct; minor overlap risk with closely related skills'; not 5 because sibling OpenSEO skills (audit, keyword-research) could overlap since no explicit trigger boundary is stated.

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-project-setup/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.