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.

72

Quality

88%

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

85%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 clean, well-structured instruction skill with a clear validated workflow and concrete action syntax. The main improvements are consolidating the slight redundancy between Core Workflow and Critical Rules and adding a reject-path example to mirror the select-path one.

Suggestions

Consolidate the 'price is strict' and 'select before buying' rules so they appear once — either inline in the Core Workflow or solely in Critical Rules — to remove the minor redundancy.

Add a short reject example showing the 'Thought: ... price too high ... Action: click[Back to Search]' path to complement the existing select-and-buy example.

Trim the worked example's Thought text slightly; the first Thought restates several already-verified facts and could be tightened while still illustrating the format.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explanation padding and assumes Claude's competence, but the Critical Rules section restates two constraints already present in the Core Workflow (strict price, select-before-buy), a minor redundancy that could be consolidated.

4 / 5

Actionability

Provides fully concrete, executable syntax ('click[value]', 'search[keywords]', 'Thought:') with exact-match rules and a worked two-turn example, but only demonstrates the matching/select path; the common reject path (click[Back to Search]) is described in rules but not shown in an example.

4 / 5

Workflow Clarity

A clear five-step sequence with explicit validation checkpoints — the strict price check with its immediate 'navigate back' reject branch and the per-attribute verification — plus a feedback loop (any failure → Back to Search), satisfying the destructive-action validation requirement since the skill is itself a pre-purchase verification.

5 / 5

Progressive Disclosure

A single, tightly scoped file with well-signaled sections (Input, Core Workflow, Action Format, Critical Rules, Example) and no bundle files; per the simple-skill exception, well-organized sections with no need for external references earn a 5.

5 / 5

Total

18

/

20

Passed

Description

92%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 well-crafted description that explicitly covers what the skill does and when to use it with concrete, domain-specific action language and broad trigger synonyms. Minor improvement possible by adding a couple of more colloquial shopping trigger phrases.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'extracting price, comparing color availability, validating specifications, and confirming option selections' — plus the concrete output protocol of a 'Thought:' assessment followed by a 'click[value]' action, giving comprehensive coverage for the domain.

5 / 5

Completeness

Explicitly answers both 'what' (verifies attributes via price extraction, color/spec/option checks with a Thought/click output) and 'when' ('Use when you need to check if a product matches requirements, verify product details before buying, confirm item specifications...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong synonym coverage (check/verify/confirm/validate) with concrete attribute terms (price, color, size, specifications), but the register is somewhat formal and lacks the most colloquial shopping phrasing a user might naturally say, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear narrow niche — verifying product attributes on a web shop detail page before purchase with a specific Thought/click[value] protocol — and its triggers ('product detail page', 'before purchase') are distinct, giving minimal conflict risk.

5 / 5

Total

19

/

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.

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.