CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

site-auditor

Audit websites by cross-referencing query indexes, sitemaps, and navigation to identify content gaps, stale pages, missing metadata, and quality issues. Use when "auditing a website", "finding content gaps", "site quality audit", or "content inventory analysis".

Quality

82%

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

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.

A highly actionable, well-sequenced audit procedure with concrete endpoints, executable code, and a complete output contract. Its main weaknesses are redundancy — category details duplicated between the body and an unlinked references/gap-categories.md, plus a Quick Reference table and When to Use section that restate the description — and the absence of an output-validation checkpoint.

Suggestions

Link the existing bundle file from Step 4 (e.g., 'See [gap-categories.md](references/gap-categories.md) for detection logic, examples, and remediation actions per category') and shrink the inline category entries to name + severity, eliminating the duplication between the body and the currently orphaned reference file.

Remove the "Quick Reference" table (it restates the description's trigger phrases and adds non-actionable metadata like "8 projects"), and trim "When to Use" to only bullets that add information beyond the frontmatter description.

Add an explicit output verification step, e.g., reconcile summary.totalUniquePages and per-category counts against the union of the three normalized path sets before writing data/audit/analysis.json and presenting results.

DimensionReasoningScore

Conciseness

Most of the body is dense and task-specific (troubleshooting table, normalizePath/isStale code, output contract), but the "Quick Reference" table ("Complexity: High", "8 projects") and "When to Use" section restate the frontmatter description, and Step 4's ~70 lines of category detail duplicate the 11.4 KB references/gap-categories.md wholesale. This fits 'mostly efficient but could be tightened' better than anchor 2's 'noticeably verbose', since roughly three-quarters of the body earns its tokens and there is no basic-concept padding.

3 / 5

Actionability

Guidance is fully executable: exact endpoints ("{origin}/query-index.json", "{origin}/query-index.json" pagination with "?offset={next}"), copy-paste-ready JavaScript (normalizePath, isStale), explicit thresholds ("shorter than 20 characters", "older than 12 months", placeholder patterns), prioritized CSS selectors, and a complete analysis.json output schema. Not 4 because common edge cases (paginated index, sitemap index, mega-menu, missing lastModified) are all concretely covered in the troubleshooting table.

5 / 5

Workflow Clarity

Eight numbered steps are clearly sequenced (collect → normalize → categorize → analyze → freshness → output → optional RUM → present) with explicit failure handling ("if one fails, proceed with the remaining sources and note the gap") and a troubleshooting table of failure modes with fixes. Not 5 because there is no validation checkpoint on the output artifact itself (e.g., reconciling summary counts against the union of normalized paths before presenting), and this batch operation's recovery guidance stops at data-source failures.

4 / 5

Progressive Disclosure

The body is well-sectioned (headers, steps, tables), but references/gap-categories.md is completely orphaned — no link or mention anywhere in the body — while its entire content is inlined in Step 4, matching the anchor-3 pattern 'references present but not clearly signaled; content that should be separate is inline'. Not 2 because the body's own structure is organized and self-contained rather than minimal; not 4 because the one bundle reference that exists is entirely unsignaled and its content duplicated.

3 / 5

Total

15

/

20

Passed

Description

83%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 voice, a clear and specific statement of what the skill does, and an explicit 'Use when' clause with natural trigger phrases. The only weaknesses are a generic "quality issues" tail and a few missing common synonyms (most notably "content audit").

DimensionReasoningScore

Specificity

"cross-referencing query indexes, sitemaps, and navigation" and "identify content gaps, stale pages, missing metadata" name several concrete actions and data sources, matching the 'several specific actions; minor gaps' anchor rather than 5 because the trailing "and quality issues" is a generic catch-all rather than a concrete finding type.

4 / 5

Completeness

It explicitly answers both questions: the "what" is "Audit websites by cross-referencing query indexes, sitemaps, and navigation to identify content gaps..." and the "when" is an explicit "Use when" clause with four concrete trigger phrases — an exact match to the anchor. Not 4 because the "when" clause is already explicit and specific, not merely improvable.

5 / 5

Trigger Term Quality

The quoted triggers "auditing a website", "finding content gaps", "site quality audit", and "content inventory analysis" are natural phrases a user would say, but common synonyms like "content audit" and "stale content" are missing, so coverage is good rather than comprehensive (anchor 4, not 5).

4 / 5

Distinctiveness Conflict Risk

The niche (cross-referencing query indexes/sitemaps/nav for content gaps and metadata issues) is clearly distinct, but the broad triggers "auditing a website" and "site quality audit" could also plausibly match closely related skills in this ecosystem (e.g., pagespeed-audit, accessibility-auditor), giving minor overlap risk per the anchor-4 example.

4 / 5

Total

17

/

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

paolomoz/skills

Path

skills/site-auditor/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.