pagination-helper
Pagination Helper - Auto-activating skill for API Development. Triggers on: pagination helper, pagination helper Part of the API Development skill category.
36
Quality
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 severely underdeveloped, consisting mostly of boilerplate category labels without any substantive content. It fails to describe what the skill actually does, provides no natural trigger terms users would say, and lacks any explicit guidance on when Claude should select this skill. The repeated 'pagination helper' trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific concrete actions like 'Implements cursor-based pagination, adds offset/limit parameters, handles page token responses, generates pagination metadata'
Include a 'Use when...' clause with natural trigger terms: 'Use when implementing paging, adding next/previous page links, handling large result sets, or when user mentions pagination, cursors, page numbers, or offset/limit'
Remove the redundant trigger term and expand to include variations users would naturally say: 'paging', 'paginate results', 'page through data', 'infinite scroll API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Pagination Helper' and 'API Development' without describing any concrete actions. There are no specific capabilities listed like 'implement cursor-based pagination' or 'add page number parameters'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague category label, and provides no explicit 'when to use' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pagination helper' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'paging', 'page numbers', 'cursor', 'offset', 'limit', or 'next page'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'pagination' is somewhat specific to a particular API concern, the lack of detail means it could overlap with general API development skills. The mention of 'API Development' category helps slightly but doesn't clearly carve out a distinct niche. | 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 a placeholder template with no actual content. It describes what a pagination helper skill would do without providing any concrete implementation guidance, code examples, or specific patterns for cursor-based, offset-based, or keyset pagination. The entire content could be replaced with a single sentence: 'This skill helps with pagination' - which would be equally (un)helpful.
Suggestions
Add concrete code examples for common pagination patterns (cursor-based, offset-based, keyset) with executable snippets for REST and GraphQL APIs
Include specific guidance on pagination parameters (page size limits, cursor encoding, total count handling) with example request/response payloads
Provide a decision tree or clear criteria for choosing between pagination strategies based on use case
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually implement pagination - no examples, no code snippets, no specific patterns. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for implementing pagination in any context. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples file, no API-specific pagination patterns. The content is both shallow and poorly organized. | 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
0c08951
- 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.