CtrlK
BlogDocsLog inGet started
Tessl Logo

icp-website-audit

End-to-end website audit through ICP eyes. Builds synthetic personas (if they don't already exist), runs a structured scorecard review of the client's site, then runs a head-to-head competitive comparison against top competitors. Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations. The complete "how do our buyers actually experience our site vs the competition?" workflow.

50

Quality

55%

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/lead-generation/composites/icp-website-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.

A well-structured, clearly sequenced orchestration skill with a thorough report template, but it is verbose and monolithic, delegates concrete execution to other skills, and lacks explicit validation checkpoints. Progressive disclosure and conciseness are the biggest opportunities.

Suggestions

Extract the consolidated report template (lines 135-322) into a reference file (e.g. references/report-template.md) and link to it from the body to improve progressive disclosure and conciseness.

Add explicit validation/feedback checkpoints in Phases 2-3 (e.g. confirm crawl coverage, sanity-check persona scores before synthesis) since this is a batch operation across multiple sites and personas.

Tighten the Tips and Parallelization sections to essentials, and make per-phase guidance less template-placeholder dependent.

DimensionReasoningScore

Conciseness

The body is mostly task-relevant and avoids explaining concepts Claude already knows, but it embeds a very large inline report template (lines 135-322) plus tips and parallelization that could be tightened or moved to references.

2 / 3

Actionability

Gives concrete phase steps, specific scoring dimensions (1-10), file paths, and a structured template, but the actual execution (crawl, fetch, score) is delegated to other skills and the report is placeholder-driven rather than copy-paste ready.

2 / 3

Workflow Clarity

Phases 1-4 are clearly sequenced with per-phase inputs/outputs and a parallelization diagram, but this batch operation (multi-site, multi-persona, multi-competitor) lacks explicit validation/feedback checkpoints beyond a light 'confirm personas look current' check, capping it at 2.

2 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a single monolithic SKILL.md with a huge inline report template that should be split into a reference file; no bundle files (references/, scripts/, assets/) are provided.

2 / 3

Total

8

/

12

Passed

Description

60%

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 capable, specific description that names concrete actions and a clear deliverable, but it lacks an explicit 'Use when...' trigger and carries some jargon and naming-collision risk. Completeness and trigger guidance are the main weaknesses.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when the user wants to evaluate their website through buyers' eyes and compare it against competitors').

Soften jargon like 'ICP eyes' and 'scorecard review' with plain-language equivalents a user would actually say.

Clarify the relationship to the dependency also named 'icp-website-audit' to reduce distinctiveness/conflict confusion.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Builds synthetic personas', 'runs a structured scorecard review', 'runs a head-to-head competitive comparison', 'Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations'.

3 / 3

Completeness

Clearly answers 'what' but provides no explicit 'Use when...' trigger clause; the 'when' is only implied by the closing question, which per guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant natural phrases like 'website audit', 'competitive comparison', and 'how do our buyers actually experience our site vs the competition', but leans on jargon ('ICP eyes', 'scorecard review') and misses common variations a user might say.

2 / 3

Distinctiveness Conflict Risk

The persona-plus-competitive-audit niche is fairly specific, but the skill name 'icp-website-audit' collides with a dependency of the same name and 'website audit' could overlap with sibling research skills.

2 / 3

Total

9

/

12

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.