CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-query-parser

This skill extracts key constraints and product requirements from a user's shopping query. It should be triggered when the agent receives a new shopping instruction, to identify product attributes (e.g., 'gluten free'), price limits (e.g., 'lower than 140.00 dollars'), and other specifications. The skill outputs a structured set of search criteria to guide subsequent product discovery.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 concise, well-structured instruction skill with clear workflow and a concrete worked example. Its main weaknesses are an un-navigated bundle reference and a referenced parser script that is not bundled.

Suggestions

Add an explicit pointer to the bundled reference, e.g. 'See references/query_components.md for the full list of attribute, price-pattern, and specification examples.'

Either bundle the referenced parse_query.py script or replace the 'Run the Parser' step with the concrete parsing rules from query_components.md so the guidance is self-contained and executable.

Link or inline a few representative natural user phrasings ('I need...', 'find me...', 'buy...') so the skill triggers on the variations users actually say.

DimensionReasoningScore

Conciseness

Lean, well-organized sections with no padding and no over-explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides a concrete parsed-output example and a specific `search[gluten free popcorn]` action, but references running a bundled `parse_query.py` script that is not actually present in the bundle, leaving a minor execution gap.

4 / 5

Workflow Clarity

For this simple single-purpose skill the sequence—When to Use, Core Task, Procedure (3 steps), Output, Notes—is unambiguous and clearly ordered; no destructive or batch operation requires validation checkpoints.

5 / 5

Progressive Disclosure

Section structure is clean and a reference file (references/query_components.md) exists, but the body never signals or links it, so the bundled reference is not navigable from the SKILL.md overview.

3 / 5

Total

17

/

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, concrete description that clearly answers both 'what' and 'when' with specific examples and minimal conflict risk. Trigger-term coverage is good but could include a few more natural phrasing variations users say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'extracts key constraints and product requirements', 'identify product attributes (e.g., gluten free)', 'price limits', 'outputs a structured set of search criteria'—with examples, giving comprehensive coverage.

5 / 5

Completeness

Explicitly states both what it does ('extracts key constraints... outputs a structured set of search criteria') and when to use it ('It should be triggered when the agent receives a new shopping instruction').

5 / 5

Trigger Term Quality

Includes natural user terms like 'shopping query', 'shopping instruction', 'gluten free', and 'lower than 140.00 dollars', but is missing common phrasing variations (e.g., 'I need', 'buy', 'find me') a user might actually say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche—parsing shopping queries into structured search criteria—with distinct triggers and minimal overlap risk against unrelated 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.