CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-attribute-selector

Selects specific product attributes (e.g., flavor, size) on a product detail page to match user requirements. Triggered when a product page presents configurable options and the parsed query specifies needed values. It identifies the correct option from available clickables (e.g., 'smoked bacon' for flavor, '4 ounce (pack of 2)' for size) and executes the selection click.

60

Quality

71%

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-attribute-selector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 compact, well-sequenced instruction skill with a clear workflow and a validation checkpoint. Its main weakness is actionability: the matching logic is offloaded to a referenced script that is not present, which also leaves a broken reference hurting progressive disclosure.

Suggestions

Either provide scripts/match_attribute.py or inline the exact/fuzzy matching rules so the selection step is fully executable without an external dependency.

Add an explicit verification step after selection (e.g., confirm the observation now shows the option as selected/highlighted) before proceeding to 'Buy Now'.

Tighten 'Important Notes' to remove guidance already implied by the Core Process steps.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence; minor over-explanation such as the dietary-feature aside and some restated points in 'Important Notes' could be trimmed.

4 / 5

Actionability

Gives a concrete action format ('click[value]') but delegates the hard part — fuzzy/exact matching — to 'scripts/match_attribute.py', whose logic is unspecified and whose file is absent from the bundle, leaving a key detail missing.

3 / 5

Workflow Clarity

Clear four-step sequence (Parse, Map, Execute, Finalize) with a validation checkpoint ('If a required attribute cannot be matched... do not click') and a loop ('Continue until all specified attributes are satisfied'); minor validation gaps remain.

4 / 5

Progressive Disclosure

Sections are well organized for a short skill, but the inline reference 'scripts/match_attribute.py' points to a file that does not exist in the bundle, a dangling navigation pointer rather than clean one-level-deep disclosure.

3 / 5

Total

14

/

20

Passed

Description

78%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-targeted description that clearly defines a narrow niche and gives concrete actions with examples. The 'when' clause is explicit but slightly internal-facing rather than user-phrase-oriented, keeping it just shy of top marks on completeness and trigger quality.

Suggestions

Reframe the trigger around natural user phrasings (e.g., 'Use when the user asks for a specific flavor, size, or dietary option on a product page') rather than 'parsed query specifies needed values'.

Add a couple of common synonyms users say ('flavor', 'size', 'dietary feature', 'pack size') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Selects specific product attributes', 'identifies the correct option from available clickables', 'executes the selection click' — with illustrative examples like 'smoked bacon' and '4 ounce (pack of 2)'.

4 / 5

Completeness

Explicitly states both what (select attributes, identify option, execute click) and when ('Triggered when a product page presents configurable options and the parsed query specifies needed values'), but the 'when' leans on internal state rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms for the domain ('product detail page', 'flavor', 'size', 'configurable options'); 'parsed query' is somewhat internal, and a few natural user phrasings are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear narrow niche — selecting configurable product attributes on a product detail page — with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.