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.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seo/capabilities/seo-traffic-analyzer/SKILL.md

Quality

Content

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

Highly actionable and clearly sequenced: a user or agent could execute the analysis immediately from the exact queries, URLs, and output template provided. The weaknesses are redundancy (duplicated intro and agent-integration workflow) and a monolithic single-file structure where the report template and keyword lists belong in reference files.

Suggestions

Move the ~55-line markdown report template (Phase 7) into a references/report-template.md file and replace it with a one-line pointer, cutting a large chunk of inline tokens.

Delete or merge the "AI Agent Integration" section into the Process overview — its 6-step workflow duplicates the seven phases already documented, and the example prompt repeats the Quick Start example.

Remove the opening paragraph that restates the frontmatter description nearly verbatim, and add per-phase guidance for handling empty or blocked search results (e.g., query variations, retry cadence) to strengthen workflow checkpoints.

Dimension	Reasoning	Score
Conciseness	The query lists are lean, but the opening paragraph restates the frontmatter description almost verbatim, the ~55-line report template is inlined wholesale, and the "AI Agent Integration" section re-describes the Process phases already covered above.	3 / 5
Actionability	Guidance is copy-paste ready throughout: exact search operators ("site:[domain] filetype:pdf"), concrete WebFetch URLs ("https://www.similarweb.com/website/[domain]/"), per-category keyword patterns, and a worked example with real domains (pump.co, vantage.sh).	5 / 5
Workflow Clarity	Seven phases are clearly sequenced with per-phase extraction targets, and a fallback is noted for SimilarWeb rate-limiting; however, no explicit per-phase validation checkpoints exist (e.g., what to do when a search returns nothing), keeping it below a 5. The skill is read-only, so the destructive/batch validation cap does not apply.	4 / 5
Progressive Disclosure	The single file is well-sectioned, but at 230+ lines with the full report template and keyword taxonomies inlined — content that clearly belongs in separate reference files — and no bundle files or references exist, organization could be significantly better.	3 / 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 description: third-person, specific about capabilities and methods, with identifiable use cases. Its main gap is the absence of an explicit "Use when..." trigger clause and a few natural trigger synonyms (backlinks, domain authority).

Dimension	Reasoning	Score
Specificity	"Analyze a website's SEO visibility, keyword rankings, traffic estimates, and competitive positioning" lists multiple concrete actions, and "Uses web search probes, SimilarWeb (free tier via web), and site: queries" names the specific methods — comprehensive coverage for the domain.	5 / 5
Completeness	The "what" is explicit and concrete, and "Useful for competitive intel, gap analysis, and reverse-engineering a company's organic acquisition strategy" provides use-case guidance, but it stops short of an explicit "Use when..." trigger clause with concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Natural terms like "SEO", "keyword rankings", "traffic estimates", and "website" are terms users would actually say, but common variations such as "backlinks", "domain authority", or "rank on Google" are missing.	4 / 5
Distinctiveness Conflict Risk	The SEO/traffic-analysis niche is clear with distinct triggers (site: queries, SimilarWeb, keyword rankings), but it sits within the broader competitive-intel research space, creating minor overlap risk with general web-research skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/seo/capabilities/seo-traffic-analyzer/SKILL.md
Commit: cc3e518

Reviewed: 7 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.