CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-audit

Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.

Quality

77%

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 ./plugins/openseo/skills/seo-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an unusually disciplined instruction-only skill: concrete tool parameters, exact output conventions, honest-sizing rules, and a well-sequenced workflow with real validation checkpoints. Its main structural weakness is that reference material (tool semantics, report format spec) is inlined in a long single file rather than offloaded to reference files.

Suggestions

Move the detailed MCP tool semantics (get_serp_results, get_ranked_keywords conventions) into a references/tools.md file, keeping a one-line summary of each tool in SKILL.md.

Move the full output-format specification and HTML skeleton into a references/report-format.md, inlining only the section list and key writing rules.

Trim the get_serp_results paragraph by moving edge-case conventions (merge behavior, seenIn handling) into the same reference file.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain judgment — tool semantics, evidence conventions, sizing rules — and assumes Claude's competence without padding or basic-concept explanations. A few spots could be trimmed (the long get_serp_results conventions paragraph, the inline canonical gloss), which keeps it at anchor 4 rather than 5.

4 / 5

Actionability

Guidance is fully executable throughout: exact tool calls with parameters (resultTypes: ["organic"], scope: "exact_url", depth 20), exact position notation rules ("#10 (page 1)"), a copy-paste-ready HTML skeleton for the deliverable, and defined columns for the opportunities.md shortlist. This matches anchor 5 — specific examples cover the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced steps (Orient, Investigate, Shortlist, Choose, Size, Review/write) with explicit validation checkpoints: re-run deciding queries before writing, complete missing lookups before ranking, a reviewer pass with a concrete checklist, verification of new factual claims, and crawl-failure investigation before anything else. This matches anchor 5; the destructive/batch cap does not apply since the audit is read-only plus report writing.

5 / 5

Progressive Disclosure

The body has good section structure but is a single ~135-line file with no bundle files, and reference-like material (the MCP tool semantics section and the full output-format specification with HTML skeleton) is inlined rather than split into separate reference files. Anchor 3 fits best: structure is present, but content that could live one level deeper is inline, and the under-50-line simple-skill exception does not apply.

3 / 5

Total

17

/

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 communicates a clear, concrete capability set for SEO auditing and reporting, but it is held back by missing trigger guidance and missing the most natural keywords. Adding an explicit "Use when..." clause and the terms "SEO" and "Google" would materially improve discoverability.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when asked for an SEO audit or SEO review of a website, or when the user wants to grow organic search traffic."

Include the word "SEO" itself (and ideally "Google" and "rankings") so the most natural user phrasings textually match the description.

Specify what the audit covers (e.g., rankings, keywords, content, technical issues) to strengthen the what-side of the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Audit a website", "investigate its real search opportunities", "deliver a short data-backed report on the few changes most likely to grow organic traffic that converts" — with only minor coverage gaps (no mention of keywords, rankings, or content analysis). It falls short of anchor 5 because the action set is not comprehensive, and above anchor 3 because it goes beyond one or two actions and each is concrete.

4 / 5

Completeness

The "what" is clear (audit a site, investigate opportunities, deliver a prioritized report), but the description contains no "Use when..." clause or equivalent explicit trigger guidance — that sentence lives in the body, not the frontmatter. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "audit", "search opportunities", and "organic traffic" are present, but the description omits the most natural trigger terms users would say — "SEO", "Google", "rankings", "keywords". This matches anchor 3 (relevant keywords present but missing common variations and synonyms) rather than 4, since the single most likely user phrase ("SEO audit") has no textual match in the description.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear organic-search niche ("real search opportunities", "organic traffic that converts") that is mostly distinct from adjacent skills. Minor overlap risk remains because "Audit a website" alone could also match performance or security audit requests, matching anchor 4 rather than 5.

4 / 5

Total

14

/

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

plugins/openseo/skills/seo-audit/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.