CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-agentic

Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

Quality

93%

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

SKILL.md
Quality
Evals
Security

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.

An exceptionally operational skill body: exact executable commands, a strictly ordered audit with priority-gated fixing, an honest-reporting ruleset, and a complete error-recovery table, all kept lean with detail correctly offloaded to six real reference files. The only weakness is a couple of fast-moving vendor/version facts stated inline in the body instead of being confined to the dated vendor-matrix reference.

DimensionReasoningScore

Conciseness

The body is dense and lean — tables for commands, priorities, and error handling, no explanations of concepts Claude already knows, and every section carries operational rules (e.g. "Never convert it to a percentage and never assume N"). It loses a point only for time-sensitive facts inlined in the body rather than confined to the dated references: "WebKit opposes it, Mozilla is neutral, and only ChatGPT desktop calls tools by default" and "The report predates Lighthouse 13.2" — minor instances of the version/vendor-date pattern the rubric penalizes, keeping it just below the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with exact flags and example values throughout: `"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run lighthouse_agentic.py <url> --strategy both --json`, `agentic_fix.py ai-catalog --publisher example.com --entry "Name|media type|url"`, and a concrete fallback `npx lighthouse@latest <url> --only-categories=agentic-browsing --output=json`. Check ids, evidence fields (`inconclusive: true`, `html_only_fallback`), and tool annotations are specified to the exact field name, matching anchor 5.

5 / 5

Workflow Clarity

The audit process is an explicitly ordered 6-step sequence ("Run the steps in this order"), fixes are priority-sequenced ("Fix in order P0, then P1. Do not recommend lower priorities while a measured P0 fails"), recommendations must state "how to confirm it worked (rerun the named check)", and the Error Handling table gives explicit recovery loops (quota exceeded → local run then `--from-json`; 429 → report not-tested and rerun later). Clear sequence, explicit validation, and feedback loops for error recovery match anchor 5.

5 / 5

Progressive Disclosure

The body is a genuine overview: it keeps only the process, priorities, and rules inline, and pushes all detail to six one-level-deep reference files, all of which exist in the bundle and are each summarized in the "Reference files" section (e.g. "references/vendor-matrix.md: dated, source-graded vendor facts and the refresh procedure"). Inline pointers are topic-matched ("Read `references/webmcp.md` first"), matching the anchor-5 pattern of well-signaled, one-level-deep references.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description: concrete two-verb action statement with a comprehensive enumeration of the audit surface, an explicit 'Use when' trigger clause, and explicit exclusions that separate it from neighboring SEO skills. The only gap is a handful of natural synonym phrases a user might use.

DimensionReasoningScore

Specificity

"Audit and fix agent readiness" names two concrete actions and then comprehensively enumerates the specific targets: "the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools" — full concrete coverage of the domain, matching the anchor-5 example's comprehensiveness rather than the 'minor gaps' of anchor 4.

5 / 5

Completeness

The 'what' is explicit ("Audit and fix agent readiness: ..." with the full enumerated list) and the 'when' is an explicit trigger clause ("Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP"). This clearly matches the anchor-5 example that answers both what and when with concrete trigger phrases; it is not the anchor-4 case of an only-weakly-specified 'when'.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: "whether AI agents can use or browse the site, or about llms.txt or WebMCP", plus "agent readiness", "robots.txt", and "Lighthouse Agentic Browsing". A few natural variations users might say are missing (e.g. "AI crawlers", "agent-ready", named agent browsers), so it sits at anchor 4 (good coverage, a few natural terms missing) rather than the synonym-complete anchor 5.

4 / 5

Distinctiveness Conflict Risk

It claims a clear niche (agent readiness for browsing AI agents) and actively disambiguates sibling skills: "Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce)". Distinct triggers (llms.txt, WebMCP, agent browsing) plus explicit exclusion boundaries give minimal conflict risk, matching anchor 5 rather than the 'minor overlap with closely related skills' of anchor 4.

5 / 5

Total

19

/

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.

Validation — 15 / 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

AgriciDaniel/claude-seo

Path

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