CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-purchase-initiator

Initiates the purchase process by clicking the buy button once a product and its options have been selected and verified against requirements. Use when you are on a product detail page, all selection criteria (price, features, options) are satisfied, and the user is ready to proceed to checkout. Confirms the final price meets budget constraints before executing click[buy now].

72

Quality

88%

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

92%

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

A concise, highly actionable single-purpose skill with an explicit verification checklist and error handling. Its one weakness is progressive disclosure: a bundle file exists in references/ but is not signaled or linked from the body.

Suggestions

Add a one-line pointer in the body (e.g., "See [trajectory_example.md](references/trajectory_example.md) for a full end-to-end execution trace") so the existing reference is discoverable and one level deep.

Consider noting in "When to Use" that this skill is the final step after search and option selection, to make its place in the larger purchase workflow explicit.

DimensionReasoningScore

Conciseness

The body is lean — "Execute the `click[buy now]` action to proceed to checkout" and a tight checklist with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Gives a fully concrete, executable action (`click[buy now]`) plus a worked example showing the exact instruction, observation, and action, leaving no ambiguity about what to do.

3 / 3

Workflow Clarity

The Verification Logic section sequences explicit checkpoints (Budget, Option Selection, Product Match) with a clear failure branch ("If any check fails, do not use this skill"), and Error Handling covers the missing-button and price-change cases — a well-formed feedback loop for a single risky action.

3 / 3

Progressive Disclosure

The skill is short and well-organized into sections, but the existing `references/trajectory_example.md` is never mentioned or linked from the body, so the reference is unsignaled rather than clearly navigable.

2 / 3

Total

11

/

12

Passed

Description

85%

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, third-person description that pairs a concrete single action with an explicit "Use when..." trigger and a budget precondition. Trigger-term naturalness is the weakest dimension — the wording is more procedural than conversational.

Suggestions

Add common user phrasings to the trigger (e.g., "Use when the user says 'buy this', 'purchase', or 'checkout' after options and budget are confirmed") to lift trigger-term quality toward natural speech.

DimensionReasoningScore

Specificity

Names a concrete action ("clicking the buy button", "click[buy now]") and the precondition ("final price meets budget constraints"), which is a specific, executable capability rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Initiates the purchase process by clicking the buy button... Confirms the final price meets budget constraints") and when ("Use when you are on a product detail page, all selection criteria... are satisfied, and the user is ready to proceed to checkout").

3 / 3

Trigger Term Quality

Phrases like "product detail page", "ready to proceed to checkout", and "buy button" are relevant, but natural user phrasings like "purchase", "buy now", "add to cart", or "checkout" are thin; it leans slightly technical.

2 / 3

Distinctiveness Conflict Risk

The trigger (product page with all options selected and budget verified, ready to checkout) carves a clear niche distinct from search/selection skills, so it is unlikely to fire for the wrong skill.

3 / 3

Total

11

/

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.