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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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 highly actionable with concrete tool calls and a well-sequenced workflow that includes validation checkpoints for risky batch writes. Minor conciseness gains are available from trimming redundancy between the guardrails and checklist.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes competence without over-explaining SEO or GSC concepts, with minor redundancy between the guardrails and earlier checklist steps that could be trimmed.	4 / 5
Actionability	Provides concrete MCP tool names, exact patch-op shapes, example file paths, a folder structure, and an output table format — specific, copy-paste-ready guidance covering common cases for an instruction/MCP skill.	5 / 5
Workflow Clarity	A clear 10-step numbered sequence with explicit validation checkpoints (verify MCP, confirm existing entries, confirm Search Console connection via get_search_console_performance) and merge-instead-of-overwrite feedback for the batch-write risk.	5 / 5
Progressive Disclosure	No bundle files exist; the self-contained skill is well-organized into clear named sections with no nested references and easy navigation, fitting the well-organized single-file anchor.	5 / 5
	Total	19 / 20 Passed

Description

75%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 with good natural keyword coverage, but it lacks an explicit "Use when…" trigger clause, capping completeness. Adding a when-to-use phrase would raise the trigger-term and completeness scores.

Suggestions

Append a "Use when…" clause stating when Claude should invoke this skill (e.g., "Use when starting SEO work on a new site or when a project's OpenSEO context is empty or stale").

Add a few more natural trigger synonyms a beginner might say, such as "SEO setup" or "project onboarding".

Keep the enumerated scope list — it is the strongest part of the description.

Dimension	Reasoning	Score
Specificity	Enumerates concrete content types ("site scope, goals, positioning, competitors, key pages, and preferences") plus two concrete actions ("MCP checks", "Search Console intake"), matching the comprehensive-coverage anchor.	5 / 5
Completeness	The "what" is clear and detailed, but there is no explicit "Use when…" or equivalent trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Natural user terms like "site scope", "goals", "positioning", "competitors", and "Search Console" are present, but a few common synonyms and a "Use when…" trigger phrase are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct OpenSEO project-context-setup niche with specific enumerated triggers, making conflict with other skills minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: c469a48

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.