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.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 clearly sequenced with a decision branch, but it is not fully actionable because the invoked script lacks an example invocation and is missing from the bundle, and the existing reference file is not linked.

Suggestions

Add a concrete, executable example invocation of `check_price.py` (e.g., `python scripts/check_price.py "$164.95" 200.00`) so the guidance is copy-paste ready.

Actually bundle `check_price.py` (under `scripts/`) so the referenced primary action exists, or remove the reference if the script is not intended to ship.

Link the existing `references/price_patterns.md` from the body (e.g., a short "See [price_patterns.md](references/price_patterns.md) for price-string formats" line) so the reference is discoverable.

DimensionReasoningScore

Conciseness

The body is lean, avoids explaining concepts Claude already knows, and every section earns its place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Step 3 names the `check_price.py` script and its inputs but provides no executable invocation example, and the referenced script is not present in the bundle, so guidance is concrete but not copy-paste ready.

2 / 3

Workflow Clarity

The four-step process is clearly sequenced with an explicit True/False decision branch and a fallback when the price is missing; for a simple skill this meets the clear-sequence anchor.

3 / 3

Progressive Disclosure

The bundled reference `references/price_patterns.md` exists but is never linked from the body, while the body references `check_price.py` which is absent from the bundle, so references are not clearly signaled.

2 / 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 specific, complete, and clearly scoped to a price-vs-budget checking niche with an explicit trigger clause. Its main weakness is trigger-term breadth, relying on a fairly narrow set of natural keywords.

Suggestions

Broaden trigger terms to cover phrasings users actually say, e.g., "Use when checking if an item is affordable, within a price limit, under $X, or within budget."

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "scans product listings or detail pages", "extracts the price", "compares it against the maximum allowed budget", "outputting a boolean decision" — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both "what" (scans, extracts, compares, outputs boolean) and "when" via the explicit trigger clause "It is triggered when evaluating a potential product for purchase."

3 / 3

Trigger Term Quality

It includes relevant natural terms ("price", "budget", "within budget") but coverage is narrow and omits common variations users would say (e.g., "affordable", "can I afford", "under $X"), so it does not reach the full-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

The niche is clearly scoped to price/budget checking on product pages with distinct triggers, making it unlikely to fire 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.