CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-traffic-analyzer

Analyze a website's SEO visibility, keyword rankings, traffic estimates, and competitive positioning. Uses web search probes, SimilarWeb (free tier via web), and site: queries to build an SEO profile without requiring paid tool subscriptions. Useful for competitive intel, gap analysis, and reverse-engineering a company's organic acquisition strategy.

62

Quality

73%

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 ./skills/seo/capabilities/seo-traffic-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 thorough, actionable SEO analysis playbook with concrete queries and a clear phased workflow. Its main weaknesses are verbosity in the output template and implicit rather than explicit validation checkpoints between phases.

Suggestions

Move the full Phase 7 output template into a references/ file and keep only a short skeleton inline, reducing body length and improving progressive disclosure.

Add brief validation/checkpoint notes between phases (e.g., 'Confirm at least N keywords probed before estimating traffic') to make the workflow's feedback loops explicit.

Tighten the Inputs table and Quick Start example to remove overlapping information.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept padding Claude already knows, but the ~50-line output template and some redundancy between the Inputs table and Quick Start example could be tightened.

3 / 5

Actionability

Provides concrete, runnable WebSearch/WebFetch queries, specific URLs (similarweb.com/website/[domain], web.archive.org), and a worked example; minor gaps remain because many queries use [domain]/[keyword] placeholders rather than fully copy-paste-ready form.

4 / 5

Workflow Clarity

A clear 7-phase sequence with each phase listing searches to run and data to extract; validation checkpoints are largely implicit rather than explicit, but the skill is read-only so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Quick Start, Inputs, Cost, Process, Tips, Limitations) with no external bundle files needed; the long inline output template is the main piece that could be split out.

4 / 5

Total

15

/

20

Passed

Description

80%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, specific description that names concrete capabilities and tools while signaling trigger contexts. It would benefit from a more explicit 'Use when...' phrasing and a few additional natural synonyms.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when analyzing a competitor's organic search presence or estimating website traffic without paid tools') to make the trigger unambiguous.

Include a few more natural user phrases/synonyms such as 'SEO audit', 'keyword positions', or 'organic traffic'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Analyze a website's SEO visibility, keyword rankings, traffic estimates, and competitive positioning' and names specific methods (web search probes, SimilarWeb, site: queries), giving comprehensive coverage.

5 / 5

Completeness

Clearly states what it does and provides equivalent trigger guidance via 'Useful for competitive intel, gap analysis, and reverse-engineering...', though the 'when' could be framed more explicitly as a 'Use when...' clause.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('SEO visibility', 'keyword rankings', 'traffic estimates', 'competitive intel', 'gap analysis'); a few common synonyms/extensions are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear SEO/traffic-analysis niche with specific free-tier tools, but 'competitive intel' is a broad category with minor overlap risk against related competitive-research skills.

4 / 5

Total

17

/

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.

Validation15 / 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
gooseworks-ai/goose-skills
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.