CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-attribute-verifier

Verifies product attributes on a web shop detail page by extracting price, comparing color availability, validating specifications, and confirming option selections against user requirements before purchase. Use when you need to check if a product matches requirements, verify product details before buying, confirm item specifications on an online store product page, or validate that price, color, size, or other attributes satisfy the user's constraints. Outputs a `Thought:` assessment followed by a `click[value]` action to select the matching option and proceed, or navigates back to search if the product does not match.

73

Quality

92%

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

92%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.

The body is an exemplary instruction-only skill: concrete action grammar, a sequenced workflow with validation checkpoints and rejection paths, and a fully worked two-turn example. Its only flaw is mild redundancy between the Core Workflow and Critical Rules sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of what a webshop or observation is; the worked example earns its tokens. The Critical Rules section ("Price is strict", "Select before buying") restates points already made in Core Workflow steps 3 and 5, which is minor over-explanation that could be trimmed, placing it between the 4 and 5 anchors but closer to 4.

4 / 5

Actionability

Fully executable guidance: exact action formats (`click[value]` with the value matching a clickable item, `search[keywords]`), a strict comparison rule, a complete two-turn worked example with a realistic Observation, and an unambiguous one-action-per-turn contract. Copy-paste ready for the target environment.

5 / 5

Workflow Clarity

A clear 5-step sequence (Parse Requirements → Inspect → Compare Price → Verify Attributes → Select or Reject) with an explicit validation checkpoint at each attribute and explicit failure-recovery branches ("navigate back immediately", "click[Back to Search] to find a different product"). The example demonstrates the loop across two turns. Not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

This is a single-purpose, self-contained skill (~60 lines) with no external references and no content that belongs in separate files. Sections (Input, Core Workflow, Action Format, Critical Rules, Example) are well-organized and easy to navigate, matching the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

87%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 that explicitly states what the skill does, when to use it with multiple concrete trigger phrases, and what it outputs. The only deductions are second-person phrasing in the trigger clause ("Use when you need to...") and a few missing natural trigger synonyms.

Suggestions

Rewrite the trigger clause in third person to match the rest of the description, e.g. "Use when the agent needs to check if a product matches requirements..." — the current "Use when you need to" uses second person voice.

Add one or two more natural user phrasings (e.g., "shopping", "online store", "product detail page") to the trigger clause to broaden keyword coverage toward the comprehensive anchor.

DimensionReasoningScore

Specificity

"extracting price, comparing color availability, validating specifications, and confirming option selections" lists multiple concrete actions with comprehensive coverage, and "Outputs a `Thought:` assessment followed by a `click[value]` action" specifies the output contract. Reduced by 1 per guideline because the trigger clause uses second person ("Use when you need to check...") instead of third person voice.

4 / 5

Completeness

Both questions are answered explicitly: the "what" is the full verification pipeline ("extracting price, comparing color availability, validating specifications, and confirming option selections") and the "when" is a concrete "Use when you need to..." clause enumerating trigger scenarios, matching the 5-point anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrase coverage — "check if a product matches requirements", "verify product details before buying", "confirm item specifications", "price, color, size" — with verb and domain synonyms (web shop / online store / product page). A few natural user phrasings like "shopping", "add to cart", or "e-commerce" are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — pre-purchase attribute verification on a webshop detail page with a Thought:/click[] output contract — so it would not naturally trigger for unrelated shopping, scraping, or general verification skills. Distinct triggers; minimal conflict risk.

5 / 5

Total

18

/

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
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.