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.

67

Quality

80%

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

92%

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

A tight, actionable, single-purpose skill body with a clear execution sequence and concrete click syntax. Its main weakness is progressive disclosure: a useful reference file exists but is unreferenced from the body and contains a broken pointer to a missing script.

Suggestions

Link references/purchase_ui_patterns.md from the 'Locate Purchase Button' step (e.g., 'See purchase_ui_patterns.md for casing, localization, and secondary button variants') so the reference is clearly signaled.

Remove or fix the reference's reference to scripts/execute_purchase.py, since no scripts/ directory exists in the bundle.

DimensionReasoningScore

Conciseness

The body is lean and sectioned (Purpose, When to Use, Core Action, Execution Logic, Important Notes, Example) with no concept-explanation fluff; it assumes Claude's competence and every section earns its place.

3 / 3

Actionability

Gives the exact executable action format ('Perform a click[purchase_button_value] action using the exact value from the available actions list') with concrete button identifiers and a copy-paste-ready worked example ('click[Buy Now]').

3 / 3

Workflow Clarity

For a simple single-action skill, the Execution Logic sequence (Locate Purchase Button -> Validate Context -> Execute Click) is clearly ordered with an explicit validation checkpoint, and the single action is unambiguous.

3 / 3

Progressive Disclosure

The body is well-organized into sections, but the provided references/purchase_ui_patterns.md is never signaled or linked from the body, and that reference itself points to a non-existent scripts/execute_purchase.py, leaving a dangling reference path.

2 / 3

Total

11

/

12

Passed

Description

67%

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 focused, third-person description with an explicit 'Use when' trigger and a concrete executable action. It is strong on completeness but narrower on specificity and trigger-term coverage, naming one action and framing triggers around internal state rather than rich user phrasings.

Suggestions

Broaden trigger-term coverage with natural user phrasings (e.g., 'checkout', 'order', 'complete the purchase') in addition to the verification-state framing.

If the skill supports more than a single click action, list those concrete actions explicitly to raise specificity; otherwise the single-action scope is accurate but limits the score.

DimensionReasoningScore

Specificity

Names the domain and a single concrete action with executable syntax ('Performs a click[Buy Now] action on the purchase button'), but lists only one action rather than multiple distinct concrete actions.

2 / 3

Completeness

Explicitly answers both what ('Executes the purchase action... Performs a click[Buy Now] action') and when via a clear 'Use when...' clause tied to verification and the decision to buy.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('buy', 'purchase', 'product', 'e-commerce'), but the trigger is framed around internal state ('verified against the user's requirements', 'decision is to buy') and misses common user variations like 'checkout' or 'order'.

2 / 3

Distinctiveness Conflict Risk

The post-verification terminal-purchase niche is fairly specific, but a single-click purchase action could still overlap with a broader checkout or cart-completion skill.

2 / 3

Total

9

/

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.