webshop-product-detail-inspector

This skill examines a product detail page to verify specific attributes or select options like size, color, or quantity. It is used after clicking on a product, to confirm that the item matches the user's needs (e.g., checking for '10 slots' option, price, material). The input is the product page observation, and the output is an action to select a required variant (e.g., click[10 slots]) or proceed if criteria are satisfied.

Quality

75%

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 ./experiments/src/skills/webshop/webshop-product-detail-inspector/SKILL.md

Quality

Content

65%

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

The skill body is concise and the core decision logic is clearly sequenced, but it is undermined by an incomplete Output Format section that promises a format never given, and by failure to reference the bundle files holding the action-pattern rules and trajectory example.

Suggestions

Complete the Output Format section by actually specifying the exact response format (e.g., Thought: ... Action: click[value]) instead of trailing off after 'in this exact format:'.

Reference references/action_guidelines.md from the Core Logic or Output Format section so the exact-match click rules and valid action patterns are discoverable.

Add a brief validation checkpoint in the Decision & Action step reminding the agent to confirm the option string exactly matches an available action before emitting click[].

Dimension	Reasoning	Score
Conciseness	The body is lean and well-structured into Purpose, Input, Core Logic, and Output Format sections with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Concrete click examples ('click[10 slots]', 'Back to Search', 'Buy Now') are present, but the Output Format section ends with 'Your response must be in this exact format:' and never provides the format, and the exact action-pattern rules live only in an unreferenced bundle file.	2 / 3
Workflow Clarity	The Core Logic is sequenced (Parse → Examine → Decision & Action) with clear decision branches, but the promised exact output format is missing and the critical 'exact match required' validation rules in action_guidelines.md are not surfaced in the workflow.	2 / 3
Progressive Disclosure	The body is organized into clear sections, but it never signals the existing bundle files (references/action_guidelines.md, references/trajectory_example.md) that contain essential detail, leaving references present but unlinked.	2 / 3
	Total	9 / 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, complete, and clearly niche-scoped, with concrete actions and an explicit when clause. Its main weakness is trigger-term quality: the phrasing is agent/workflow-oriented rather than mirroring what a user would naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'examines a product detail page to verify specific attributes or select options', 'select a required variant (e.g., click[10 slots])', and 'proceed if criteria are satisfied' — rather than vague language.	3 / 3
Completeness	Answers both what (examine/verify attributes, select variants) and when via the explicit trigger guidance 'It is used after clicking on a product, to confirm that the item matches the user's needs', which is an equivalent 'Use when...' clause.	3 / 3
Trigger Term Quality	Contains relevant terms ('product detail page', 'select options', 'size, color, or quantity') but they are agent/process-oriented rather than natural user phrasing, and common variations a user would actually say are missing.	2 / 3
Distinctiveness Conflict Risk	The narrow niche of inspecting a webshop product detail page to select a specific variant is clearly distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: zjunlp/SkillNet
Path: experiments/src/skills/webshop/webshop-product-detail-inspector/SKILL.md
Commit: 7bb9a48

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