pagination-helper
Pagination Helper - Auto-activating skill for API Development. Triggers on: pagination helper, pagination helper Part of the API Development skill category.
36
3%
Does it follow best practices?
Impact
99%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/pagination-helper/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, consisting essentially of a title and category label repeated with no substantive content. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from a generic API skill in a large skill library.
Suggestions
Add specific concrete actions such as 'Implements cursor-based pagination, offset/limit pagination, and keyset pagination for REST API endpoints. Generates page navigation logic and response metadata.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about paginating API responses, adding pagination to list endpoints, implementing cursor-based or offset pagination, or mentions page size, next page tokens, or paginated results.'
Remove the redundant 'pagination helper' trigger duplication and replace with varied natural language terms users would actually use, such as 'paginate', 'paging', 'page through results', 'API list endpoint', 'cursor', 'offset/limit'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Pagination Helper' and 'API Development' without describing any concrete actions. There are no specific capabilities listed such as implementing cursor-based pagination, adding page parameters, or handling offset/limit patterns. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or equivalent trigger guidance). It only states a category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'pagination helper' repeated twice. It misses natural terms users would say like 'paginate', 'page size', 'cursor', 'offset', 'limit', 'next page', 'API pagination', or 'list endpoint'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'pagination' is somewhat specific to a niche area, which provides some distinctiveness. However, the lack of detail about what kind of pagination (API response pagination, UI pagination, database pagination) means it could overlap with frontend or database skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content. It describes what a pagination helper skill would theoretically do but provides zero concrete guidance, code examples, or implementation details for any pagination pattern (cursor-based, offset-based, keyset, etc.). It is entirely non-functional as a skill.
Suggestions
Add concrete, executable code examples for common pagination patterns (cursor-based, offset-based, keyset) in at least one language/framework
Include specific implementation guidance such as SQL query patterns, API response schemas, and link header formats for REST pagination
Remove all meta-descriptive sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actual step-by-step implementation workflows
Add validation steps such as how to test pagination edge cases (empty pages, last page, invalid cursors) to ensure correctness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill supposedly does without providing any actual instructions, code, or concrete guidance. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of pagination implementation. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are claims about capability without any actual guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill contains no process for implementing pagination in any form. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed materials, and no navigation structure. The sections that exist are purely meta-descriptive boilerplate with no substance to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.