CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-product-detail-navigator

Navigates to and interacts with a specific product's detail page. This skill is triggered after a candidate product ID is selected from search results. It performs the click action to load the product page and then identifies available interactive elements (like flavor or size selectors) that need to be configured to match the user's requirements.

59

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/webshop/webshop-product-detail-navigator/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.

The body is well-structured and reasonably lean with a clear workflow and validation notes, but its actionability and progressive disclosure are undermined by a referenced script (configure_product.py) that is absent from the bundle and an unlinked reference file. Tightening these would materially raise the score.

Suggestions

Either bundle the referenced configure_product.py under scripts/ or replace the 'Use it to generate the correct click actions' instruction with the explicit, self-contained selection logic so the skill is actionable without the missing script.

Link the existing reference explicitly (e.g., 'See [action_protocol.md](references/action_protocol.md)') and remove the duplicated Action Format content from the body to avoid redundancy.

Add a short validate-fix-retry checkpoint after configuration (e.g., re-read observation, confirm the selected option is reflected, retry if not) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean and does not over-explain concepts Claude knows, but the 'Action Format' section duplicates content that also lives in references/action_protocol.md and could be tightened. It is not score 3 because of this redundancy; not score 1 because it avoids verbosity and concept padding.

2 / 3

Actionability

Provides concrete action formats and examples ('click[<exact_value>]', product ID 'B06Y96MXJV'), but defers the core deterministic logic to 'configure_product.py', a bundled script that does not exist in the skill. It is not score 3 because the key tool it tells Claude to use is missing and the guidance is therefore incomplete.

2 / 3

Workflow Clarity

A clear five-step Core Workflow is present with validation notes ('Do not click an option if it does not appear in the current list of clickables', 'Always read the full observation after each action'), but the per-step configuration detail is deferred to the absent script and there is no structured validate-fix-retry feedback loop. It is not score 3 because checkpoints are advisory rather than structured with error-recovery loops.

2 / 3

Progressive Disclosure

Content is organized into clear sections (Purpose, When to Use, Core Workflow, Action Format, Key Logic, Important Notes), but the body references a bundled script 'configure_product.py' that is not present and never links the existing references/action_protocol.md. It is not score 3 because navigation to bundle materials is incomplete and a referenced path is dangling.

2 / 3

Total

8

/

12

Passed

Description

85%

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

The description is specific, third-person, and explicitly covers both what the skill does and when it triggers, with a clear niche. Its main weakness is trigger-term breadth: the keywords are domain-locked and system-oriented rather than spanning natural user phrasings.

Suggestions

Add a user-facing 'Use when...' clause with natural phrasings (e.g., 'Use when you need to open a product page and pick the right flavor or size') to broaden trigger-term coverage.

Include common natural variations of the trigger terms (e.g., 'product page', 'item details', 'select options') alongside the system-oriented wording.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Navigates to and interacts with a specific product's detail page', 'performs the click action to load the product page', 'identifies available interactive elements (like flavor or size selectors)'. It is not score 2 because the actions are specific and varied rather than a single domain/action pair.

3 / 3

Completeness

Clearly states what it does and gives an explicit trigger — 'This skill is triggered after a candidate product ID is selected from search results'. It is not score 2 because the 'when' is explicitly stated rather than missing or merely implied.

3 / 3

Trigger Term Quality

Contains relevant domain keywords ('product's detail page', 'product ID', 'search results', 'flavor or size selectors') but they are narrow and system-oriented, missing the common natural variations and breadth seen in the score-3 anchor. It is not score 3 because coverage of terms a user would naturally say is limited.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (webshop product-detail navigation and option configuration) with distinct triggers unlikely to overlap with unrelated skills. It is not score 2 because it is not merely a broad domain label.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zjunlp/SkillNet
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.