CtrlK
BlogDocsLog inGet started
Tessl Logo

webshop-result-page-navigator

Navigates through paginated search results by moving to the next or previous page. Use this skill when the current page of product listings does not contain a suitable match and you need to review more options. It identifies and clicks the appropriate pagination controls (e.g., 'next >' or '< prev') to load additional result pages for evaluation.

62

Quality

73%

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-result-page-navigator/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.

The body is a compact, reasonably actionable overview with a clear step sequence, but it carries redundant narrative and rationale that could be trimmed, and critically fails to link the accompanying pagination_controls.md reference that contains supporting detail. Adding a signaled pointer to the reference and tightening the trajectory/principle sections would materially improve it.

Suggestions

Add an explicit reference link to references/pagination_controls.md (e.g., 'See [pagination_controls.md](references/pagination_controls.md) for control identification and presence-check details') so the bundle file is discoverable from the body.

Trim the 'Usage in Trajectory' narrative and 'Key Principle' rationale, or condense them into a one-line example, to remove redundancy with the description and conceptual padding Claude already knows.

Add an explicit validation checkpoint in Core Logic (e.g., confirm the target control appears in the observation before emitting the click) to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

Mostly efficient but includes unnecessary explanation: the Purpose section restates the description's trigger, the 'Usage in Trajectory' narrative over-specifies a pendant-light example, and the 'Key Principle' section explains rationale Claude already understands.

3 / 5

Actionability

Provides concrete executable commands `click[next >]` and `click[< prev]` covering the common cases, with a worked example; minor gaps include no in-body guidance on confirming a control is present before clicking.

4 / 5

Workflow Clarity

Core Logic lays out a clear 3-step sequence (Trigger Condition → Action Selection → Post-Action) appropriate for this simple skill, but lacks an explicit validation checkpoint confirming the pagination control exists before execution.

4 / 5

Progressive Disclosure

The body is sectioned well, but the bundle file references/pagination_controls.md (which holds control-identification detail and presence checks) is never referenced or linked from the body, so a provided reference is present but not clearly signaled.

3 / 5

Total

14

/

20

Passed

Description

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

The description is strong: it explicitly covers what the skill does and when to use it with concrete trigger phrasing and specific control examples. Its main limitation is the inherently narrow, single-purpose scope of pagination navigation, which limits action coverage and creates minor overlap risk with broader web-navigation skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'moving to the next or previous page', 'identifies and clicks the appropriate pagination controls (e.g., next > or < prev)' — with specific clickable values, but coverage is narrow for a single-purpose skill.

4 / 5

Completeness

Explicitly answers both what ('Navigates through paginated search results... identifies and clicks the appropriate pagination controls') and when via a concrete 'Use this skill when the current page of product listings does not contain a suitable match' trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('product listings', 'next or previous page', 'review more options') with good keyword coverage, though common variations like 'browse more results' or 'see more' are missing.

4 / 5

Distinctiveness Conflict Risk

The WebShop product-listing pagination niche is mostly distinct with a clear trigger, but 'next/previous page' navigation is a generic web concept with minor overlap risk against general web-navigation skills.

4 / 5

Total

17

/

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.