webshop-purchase-executor

Executes the purchase action for a confirmed suitable product on an e-commerce page. Use when a product has been verified against the user's requirements (price, attributes) and the decision is to buy. Performs a click[Buy Now] action on the purchase button to complete the transaction.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/webshop/webshop-purchase-executor/SKILL.md

Quality

Content

65%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 skill body is a clean, well-organized single-purpose instruction with a concrete worked example. Its weaknesses are the absence of a genuine validation feedback loop for a committed purchase action and a reference bundle file that is never referenced from the body.

Suggestions

Add an explicit validation/re-check step before executing the click (e.g. confirm button text and that verification passed) with a retry path on failure.

Link the existing references/purchase_ui_patterns.md from the body so the bundle is clearly signaled and discoverable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections and a concrete example, with only minor redundancy between Purpose, When to Use, and Important Notes; it does not explain concepts Claude already knows, fitting the 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	Provides concrete, executable guidance with the exact action format 'click[purchase_button_value]' and a fully worked scenario ending in 'click[Buy Now]', with only minor gaps, matching the 'mostly executable guidance' anchor rather than the fully copy-paste-ready 5.	4 / 5
Workflow Clarity	Steps are sequenced (Locate, Validate Context, Execute) but the validation checkpoint is weak ('Ensure... the prior verification step is logically complete') with no feedback loop; since a purchase is a terminal/committed action, the missing validation gap fits the 'steps listed but validation gaps' anchor and the destructive-op cap at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned and a real one-level reference file (purchase_ui_patterns.md) exists, but the body never cites or links it, so the reference is present yet not clearly signaled, matching the 'some structure... references present but not clearly signaled' anchor.	3 / 5
	Total	14 / 20 Passed

Description

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

The description is clear and reasonably specific about a single terminal purchase action, with an explicit 'Use when' clause that answers both what and when. Its main weakness is limited action coverage and trigger-term variety, which keep it in the mid range rather than top.

Suggestions

Broaden the action coverage beyond a single click, e.g. mention 'Add to Cart' and 'Checkout' handling, to raise specificity.

Add more natural trigger phrases users would say (e.g. 'checkout', 'add to cart', 'complete the order') to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	Names the e-commerce purchase domain and a couple of concrete actions ('Executes the purchase action', 'Performs a click[Buy Now] action'), but coverage is essentially one action rather than several, matching the '1-2 concrete actions' anchor and not the multi-action 4.	3 / 5
Completeness	Clearly states what it does ('Executes the purchase action', 'Performs a click[Buy Now]') and when to use it ('Use when a product has been verified... and the decision is to buy'), but the 'when' is procedural rather than framed as concrete natural trigger phrases, so it stops short of 5.	4 / 5
Trigger Term Quality	Includes relevant terms like 'buy', 'purchase', and 'verified', but misses common variations a user would actually say such as 'add to cart' or 'checkout', fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct (terminal purchase after verification), with only minor overlap risk against closely related shopping skills like search or comparison, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 20 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-purchase-executor/SKILL.md
Commit: cce11c3

Reviewed: 2 days 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.