CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-price-checker

This skill scans product listings or detail pages to verify if an item's price meets a specified budget constraint. It is triggered when evaluating a potential product for purchase. It extracts the price from the displayed information (e.g., '$164.95') and compares it against the maximum allowed budget, outputting a boolean decision on whether the item is within budget.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./experiments/src/skills/webshop/webshop-price-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A compact, well-sequenced instruction body for a simple read-only skill, but it leans on a script that is missing from the bundle and fails to link the reference file that does exist. Adding the actual script invocation and referencing the patterns file would close the main gaps.

Suggestions

Add the concrete command for running the script (e.g., `python scripts/check_price.py --price "$164.95" --budget 200.00`) so the Execute Check step is copy-paste executable, and include the script in the bundle.

Link the existing reference from the body, e.g. 'See [price_patterns.md](references/price_patterns.md) for common price string formats and budget phrasings', so the bundled reference is actually discoverable.

Tighten the Notes by removing the redundant budget-phrasing example already covered in the reference file, keeping the body focused on the decision logic.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, with only minor over-explanation such as 'The budget is typically expressed as a dollar amount (e.g., lower than 200.00 dollars)' that could be trimmed.

4 / 5

Actionability

Names the concrete script 'check_price.py' and its inputs but gives no executable invocation (e.g., command line or argument syntax), and the referenced script is not present in the bundle, leaving key execution details missing.

3 / 5

Workflow Clarity

A clear four-step sequence (Identify Budget, Locate Price, Execute Check, Make Decision) with a True/False decision branch and a price-not-found fallback; this is a read-only check so the destructive-operation validation cap does not apply, though explicit checkpoints are minimal.

4 / 5

Progressive Disclosure

The body is well-sectioned into Process and Notes, but the bundled 'references/price_patterns.md' is never linked from the body and the 'check_price.py' script the body depends on is absent from the bundle, leaving references unsignaled and a dangling path.

3 / 5

Total

14

/

20

Passed

Description

92%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, third-person description that clearly conveys both capability and trigger conditions with concrete actions and a worked price example. Only minor gap is missing a few natural budget phrasings users might say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'scans product listings or detail pages', 'extracts the price', 'compares it against the maximum allowed budget', 'outputting a boolean decision' — covering the full workflow comprehensively.

5 / 5

Completeness

Explicitly states both what it does (scan/extract/compare/output boolean) and when to use it via the explicit trigger clause 'It is triggered when evaluating a potential product for purchase.'

5 / 5

Trigger Term Quality

Includes natural terms like 'price', 'budget', 'product', 'purchase', and a concrete '$164.95' example, but omits common variations users say such as 'under $X', 'within budget', or 'affordable'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — price-vs-budget verification for purchase decisions — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.