CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

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-purchase-executor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 delivers highly actionable, example-backed guidance for a simple single-action skill, with a clear sequence and an explicit validation checkpoint. Its weaknesses are repeated restatement of the verification prerequisite, no error-recovery guidance for a failed purchase click, and an orphaned reference file that is never linked from the skill.

Suggestions

Link references/purchase_ui_patterns.md from the body (e.g., under Execution Logic) so the bundled button-pattern catalog is discoverable, and remove or fix its mention of the nonexistent execute_purchase.py script.

State the verification prerequisite once (in 'When to Use') and cut the repeats in Purpose, Important Notes, and Validate Context.

Add a brief failure path: what to do if no purchase button is present or the click does not complete the transaction.

DimensionReasoningScore

Conciseness

Mostly efficient with no beginner-concept padding, but the verification prerequisite is restated three times (Purpose, 'When to Use -> Prerequisite', and 'Important Notes') and again in 'Validate Context', so the body could be tightened.

3 / 5

Actionability

Fully executable guidance for the agent-action format: exact command pattern 'click[purchase_button_value]' using the value from the available actions list, concrete button identifiers, an explicit tie-break rule ('prefer the most direct path... typically "Buy Now"'), and a worked Thought/Action/Observation example ending in 'click[Buy Now]'.

5 / 5

Workflow Clarity

Clear Locate -> Validate Context -> Execute sequence with an explicit pre-transaction checkpoint, but there is no feedback loop for failure cases (button absent, click rejected) on an irreversible transaction.

4 / 5

Progressive Disclosure

The body itself is well-sectioned and short, but the bundled references/purchase_ui_patterns.md is never referenced or linked from SKILL.md, and that file in turn points to a nonexistent 'execute_purchase.py' script, leaving navigation to the bundle broken.

3 / 5

Total

15

/

20

Passed

Description

76%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 clearly delimits a narrow, single-action skill with an explicit and specific 'Use when' clause. Its main weaknesses are moderate trigger-term coverage (missing checkout/cart/order synonyms) and slight redundancy between the opening and closing sentences.

Suggestions

Add natural trigger synonyms such as 'checkout', 'add to cart', or 'order' to broaden keyword coverage.

Merge the redundant opening and closing sentences ('Executes the purchase action...' / 'Performs a click[Buy Now] action...') into one statement of the what.

Clarify distinction from adjacent cart/checkout skills by stating it is the terminal buy step, not cart management.

DimensionReasoningScore

Specificity

Names concrete actions with exact command syntax ('Performs a click[Buy Now] action on the purchase button to complete the transaction') plus verification conditions (price, attributes), though the first and third sentences redundantly restate the same action.

4 / 5

Completeness

Explicitly answers both 'what' (executes the purchase via a click[Buy Now] action) and 'when' ('Use when a product has been verified against the user's requirements (price, attributes) and the decision is to buy') with concrete, condition-based triggers.

5 / 5

Trigger Term Quality

Includes relevant keywords ('purchase', 'buy', 'Buy Now', 'price', 'e-commerce') but misses common variations and synonyms users would naturally say such as 'checkout', 'add to cart', 'order', or 'shop'.

3 / 5

Distinctiveness Conflict Risk

The post-verification, decision-to-buy trigger carves a clear terminal-purchase niche distinct from browsing/search skills, but 'executes the purchase action' retains minor overlap risk with closely related cart or checkout skills.

4 / 5

Total

16

/

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.