CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-site-health-audit

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis.

60

Quality

70%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/seo-site-health-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured strategic framework for triaging SEO audit findings, with a genuinely useful three-axis prioritization model and triage matrix. Its main weaknesses are the lack of concrete executable examples (no specific tool commands, no worked example of triaging real issues) and moderate verbosity in sections that repeat the core concepts. The skill reads more like a consulting playbook than a tool-usage skill, which limits its actionability score.

Suggestions

Add a concrete worked example showing 3-5 real Ahrefs issues being triaged through the matrix, with specific inputs and the resulting priority assignments.

Include specific Ahrefs MCP commands or API calls for pulling crawl data, tiering URLs by traffic, and filtering issues by category.

Move the detailed mechanism impact tables and failure patterns to the referenced issue-impact-table.md file to reduce the main skill's length and improve progressive disclosure.

Add explicit validation checkpoints in the workflow (e.g., 'Verify all Tier 1 URLs are accounted for before proceeding to step 3').

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but includes some content that could be tightened. The 'When to use' / 'When NOT to use' sections add moderate value but are somewhat verbose. The failure patterns section, while useful, repeats concepts already covered in the triage framework. The tables for mechanism impact are genuinely useful and earn their tokens, but overall the skill could be ~30% shorter without losing actionable content.

2 / 3

Actionability

The framework is well-defined with clear axes and a concrete triage matrix, which is genuinely actionable. However, there are no executable code examples, no specific Ahrefs MCP commands or API calls, and no concrete example of applying the matrix to a real crawl result (e.g., 'Given these 5 issues from Ahrefs, here's how they'd be triaged'). The guidance is specific enough to follow but lacks the copy-paste readiness of a score-3 skill.

2 / 3

Workflow Clarity

The 10-step workflow is clearly sequenced and includes a re-crawl verification step at the end. However, there are no explicit validation checkpoints between steps (e.g., 'confirm URL tiering is complete before proceeding to categorization'), and the measurement step (step 8) is mentioned but not given concrete examples of what metrics to check or how. For a process involving batch operations on potentially thousands of URLs, the lack of intermediate validation caps this at 2.

2 / 3

Progressive Disclosure

The skill references one external file (references/issue-impact-table.md) which is appropriate for detailed mapping tables, and cross-references other skills (seo-traffic-diagnosis, seo-onpage, seo-technical, seo-audit-orchestration). However, the bundle has no files provided, so the referenced file cannot be verified. The main content is quite long (~200+ lines) and some sections like the detailed mechanism tables and failure patterns could potentially be moved to reference files to keep the main skill leaner.

2 / 3

Total

8

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and completeness, clearly specifying both what the skill does and when to use it. The main weakness is that the 'what' portion could be more specific about concrete actions and outputs beyond the high-level 'triage by SEO impact' framing. Overall, it would perform well in a multi-skill selection scenario.

Suggestions

Add 2-3 more specific output actions to the 'what' portion, e.g., 'categorizes issues into impact tiers, estimates traffic uplift potential, and produces a prioritized sprint backlog of technical fixes.'

DimensionReasoningScore

Specificity

The description names the domain (technical SEO triage from Ahrefs Site Audit) and the core action (triage by SEO impact, not just severity), but it doesn't list multiple concrete actions beyond 'triage' — it doesn't specify what outputs it produces or specific steps like 'categorize issues by impact tier, estimate traffic uplift, create prioritized fix list.'

2 / 3

Completeness

Clearly answers both 'what' (triage technical SEO findings by SEO impact) and 'when' (explicit 'Use this skill when...' clause with multiple trigger scenarios, plus a 'Triggers on' list). Both dimensions are well-covered with explicit guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'site audit results', 'crawl errors', 'technical SEO triage', 'prioritize technical issues', 'what should we fix first', 'broken links', 'redirect chains', 'decision paralysis'. These are terms users would naturally use when facing this problem.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — it targets a specific niche (technical SEO crawl triage from Ahrefs-style tools) with domain-specific triggers like 'crawl errors', 'redirect chains', 'site audit results'. Unlikely to conflict with general SEO content skills or generic prioritization skills.

3 / 3

Total

11

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-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.