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.

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

77%

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

A clear, actionable body for a simple navigation skill with a well-sequenced core logic. Its main weakness is progressive disclosure: a reference bundle file exists but is neither linked from the body nor cleanly separated from duplicated inline content, and some sections restate the description or add editorial padding.

Suggestions

Link the reference from the body (e.g., 'See references/pagination_controls.md for control identification and action syntax') and move the duplicated syntax details there instead of restating them inline.

Trim the Key Principle section's editorial justification and remove the Purpose paragraph that restates the frontmatter description to tighten token use.

Add a one-line pre-action validation note in Core Logic (confirm the pagination control is present in the Observation before clicking) so the checkpoint lives in the main body rather than only the reference.

DimensionReasoningScore

Conciseness

The body is short and mostly tight, but the Purpose section restates the frontmatter description and the Key Principle section is an editorial justification ('freeing the agent's reasoning capacity') that could be trimmed.

2 / 3

Actionability

Provides concrete, copy-paste-ready action syntax (`click[next >]`, `click[< prev]`) and a worked trajectory example (pendant light under $120 → Page 2 → Page 3), giving specific executable guidance.

3 / 3

Workflow Clarity

For a simple single-purpose skill, the Core Logic gives a clear 3-step sequence (Trigger Condition → Action Selection → Post-Action) with an explicit pre-condition check; no destructive/batch validation gap applies here.

3 / 3

Progressive Disclosure

The body is well-sectioned, but the provided reference file references/pagination_controls.md is never linked or signaled from the body, and its content (control format, action syntax) overlaps with inline body content rather than being appropriately split and navigated to.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concisely states concrete actions, an explicit use-when trigger, and natural keyword coverage within a distinct niche. No fluff or over-claims; nothing material missing.

DimensionReasoningScore

Specificity

Lists concrete actions — 'moving to the next or previous page', 'identifies and clicks the appropriate pagination controls (e.g., 'next >' or '< prev')', 'load additional result pages' — with specific syntax examples rather than vague language.

3 / 3

Completeness

Clearly states what it does ('Navigates through paginated search results...') and an explicit 'Use this skill when...' clause defining the trigger condition, satisfying both what and when.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — 'next or previous page', 'review more options', 'current page of product listings does not contain a suitable match' — alongside the specific control syntax, giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a narrow niche (WebShop paginated result navigation) with a distinct trigger (no suitable match on current listings page), making conflict with other skills unlikely.

3 / 3

Total

12

/

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.