sorting-parameter-handler
Sorting Parameter Handler - Auto-activating skill for API Development. Triggers on: sorting parameter handler, sorting parameter handler Part of the API Development skill category.
34
0%
Does it follow best practices?
Impact
100%
1.02xAverage 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/sorting-parameter-handler/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It names the skill and its category but provides zero information about what it does, when to use it, or what user requests should trigger it. It follows a boilerplate template pattern ('Auto-activating skill for...') that adds no value for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Parses, validates, and transforms sorting parameters in API query strings, handling sort direction, multi-field sorting, and default sort configuration.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to implement sorting in an API endpoint, handle sort query parameters, parse orderBy fields, or configure ascending/descending sort logic.'
Replace the duplicated trigger term with diverse natural keywords users would actually say, such as 'sort', 'order by', 'query parameter sorting', 'sort direction', 'pagination sorting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Sorting Parameter Handler') and its category ('API Development') but provides no concrete actions. There is no indication of what the skill actually does—no verbs describing specific capabilities like parsing, validating, or transforming sorting parameters. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sorting parameter handler' repeated twice, which is not a natural phrase a user would say. Missing natural terms like 'sort', 'order by', 'query parameters', 'sort direction', 'ascending', 'descending', 'API sorting', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'API Development' is extremely broad, and without specific actions or clear triggers, this could easily conflict with any other API-related skill. | 1 / 3 |
Total | 4 / 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 template with no substantive content. It contains no actual guidance on sorting parameter handling—no code examples, no API patterns (query string sorting, multi-field sorting, sort direction handling), no concrete instructions of any kind. Every section is generic boilerplate that could be auto-generated for any topic.
Suggestions
Add concrete, executable code examples showing how to implement sorting parameters in REST APIs (e.g., parsing `?sort=name:asc,created_at:desc`, validating allowed sort fields, applying sorts to database queries).
Define a clear workflow: 1) Parse sort parameters from request, 2) Validate against allowed fields, 3) Sanitize to prevent injection, 4) Apply to query builder—with specific code for each step.
Include concrete patterns for common frameworks (Express, FastAPI, etc.) with copy-paste ready middleware/decorator examples for sorting parameter handling.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about sorting parameter design patterns, edge cases, and security considerations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about sorting parameters, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of sorting parameter patterns, no API design specifics. Every bullet point is vague and abstract (e.g., 'Provides step-by-step guidance' without any actual steps). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. There are no bundle files to reference either. | 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
3a2d27d
- 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.