CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-variant-chooser

This skill selects a product variant (e.g., size, quantity) from available options on a product detail page. It is triggered when a product page displays multiple choices, assessing the options (like '1.1 pound (pack of 1)' or 'pack of 2') and selecting one that aligns with user needs, often defaulting to a standard single unit if unspecified.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A compact, well-structured instruction body with a clear decision workflow and a real one-level reference. Its main weakness is the incomplete Action Format section, which promises a strict response format but provides none, undercutting actionability.

Suggestions

Complete the "## Action Format" section: after "Your response must strictly follow this format:" include the exact required `click[value]` template plus a filled example (e.g., observation → chosen variant → final action).

Turn the implicit price-compliance check into an explicit validation step — specify what to do when a variant's price is not displayed (e.g., click the variant first, then re-check the constraint before finalizing).

Signal the trajectory reference as a navigable link (e.g., "See [trajectory.md](references/trajectory.md) for a worked example") so the deferred material is clearly discoverable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not re-explain what a product page or variant is, and every section carries instruction rather than filler.

3 / 3

Actionability

It gives concrete guidance (the `click[value]` action, variant examples like "1.1 pound (pack of 1)"), but the "## Action Format" section ends with "Your response must strictly follow this format:" and supplies no format, leaving the key executable detail missing.

2 / 3

Workflow Clarity

The Core Decision Logic is a clear three-step sequence (Parse → Assess → Select) with a price-compliance check and an ambiguity feedback loop (click to see updated details before finalizing); for this simple single-action skill the workflow is unambiguous.

3 / 3

Progressive Disclosure

Content is organized into short, focused sections and defers the worked example to a real one-level reference ("as shown in the trajectory", which exists as references/trajectory.md), keeping the overview compact.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concisely states concrete capabilities, an explicit trigger, and a distinct niche without padding or over-claims. It clearly answers both what the skill does and when it should activate.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "selects a product variant (e.g., size, quantity)", "assessing the options", "selecting one that aligns with user needs", and "defaulting to a standard single unit" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("selects a product variant … selecting one that aligns with user needs") and when ("It is triggered when a product page displays multiple choices"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would reference — "product variant", "size", "quantity", and "product detail page" — giving good coverage of how the need is expressed.

3 / 3

Distinctiveness Conflict Risk

Has a clear, narrow niche — choosing among variant options on a product detail page via click[value] — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.