CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-action-executor

This skill executes a specific interface action, such as clicking a button or selecting an option, within a web shopping environment. It should be triggered when a decision has been made (e.g., to choose a color or proceed to purchase). The input is the target action identifier (e.g., 'white' or 'buy now'), and the output is the corresponding formatted action command (e.g., click[white]).

66

Quality

78%

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

Quality

Content

72%

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

The body is concise and well-organized for a simple single-task skill, but the Core Instruction is cut off mid-sentence, leaving the primary worked example incomplete. Completing step 2 would raise both actionability and workflow clarity.

Suggestions

Complete the truncated 'Format Output' step with a concrete example (e.g., 'For target_action "white", output: click[white]; for "buy now", output: click[buy now]; for keywords, output: search[keywords]').

Add a brief mapping rule clarifying when to use click[value] vs search[keywords] so the single action is unambiguous.

Optionally include a one-line validation note that the output must exactly match an available action on the current page.

DimensionReasoningScore

Conciseness

The body is short and lean with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Concrete format guidance exists ('click[value]' or 'search[keywords]'), but the Core Instruction step 2 is truncated mid-sentence at 'WebShop environment:' with no worked example, leaving key details missing.

2 / 3

Workflow Clarity

A two-step sequence is listed, but step 2 ('Format Output') is incomplete due to truncation, so the core formatting instruction is not fully delivered.

2 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and the content is well-organized into Purpose, When to Use, and Core Instruction sections.

3 / 3

Total

10

/

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.

The description is concise, third-person, and clearly states both what the skill does and when to use it, with concrete action and output examples. Trigger term coverage is the weakest dimension, relying on generic phrasing rather than a rich set of natural keywords.

Suggestions

Broaden trigger terms with more natural variations a user might say (e.g., 'click item', 'select option', 'add to cart', 'submit search') to improve trigger_term_quality.

Consider naming the second command form (search[keywords]) in the description so both supported actions are visible at a glance.

DimensionReasoningScore

Specificity

Names concrete actions ('clicking a button or selecting an option') and gives a concrete output example 'click[white]', listing specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers what ('executes a specific interface action... output is the corresponding formatted action command') and when ('It should be triggered when a decision has been made').

3 / 3

Trigger Term Quality

Includes relevant trigger phrasing ('to choose a color or proceed to purchase') but the keywords are somewhat generic and miss common natural variations a user might say.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear WebShop-specific niche with a distinct command format (click[value]/search[keywords]), making it unlikely to trigger for unrelated skills.

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.