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 template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses, validates, and applies sorting parameters in API endpoints, handling sort field names, directions (asc/desc), and multi-field sorting logic.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when building API endpoints that accept sorting/ordering query parameters, implementing sort logic, or handling ?sort=field&order=asc patterns.'
Include natural keyword variations users would actually say, such as 'sort', 'order by', 'query parameter sorting', 'API sort', 'pagination sorting', 'sort direction', 'ascending', 'descending'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Sorting Parameter Handler') and its category ('API Development') but describes no concrete actions. There are no specific capabilities listed such as 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 functionality and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('sorting parameter handler, sorting parameter handler'). No natural user keywords like 'sort', 'order by', 'query parameters', 'API sorting', or 'sort direction' are included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'sorting parameter handler' is a somewhat specific concept, the description is so vague that it provides no clear niche. The broad 'API Development' category label could overlap with many other API-related skills. | 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 that provides no actual content about sorting parameter handling. It repeatedly restates its own name without offering any concrete guidance, code examples, API patterns, or actionable instructions. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to implement sorting parameters in REST/GraphQL APIs (e.g., parsing `?sort=name:asc,date:desc`, building SQL ORDER BY clauses, or GraphQL sorting input types).
Define a clear workflow for implementing sorting: parse parameters → validate allowed fields → sanitize against injection → apply to query → return sorted results with metadata.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that just repeat the skill name, and replace with actual technical content covering common patterns like multi-field sorting, sort direction handling, and default sort behavior.
Add specific examples of sorting parameter schemas (e.g., OpenAPI spec snippets) and link to a reference file for advanced patterns like cursor-based pagination with sorting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate with zero substantive information. Every section restates the skill name without adding any actual knowledge or guidance that Claude doesn't already have. | 1 / 3 |
Actionability | There is no concrete code, no specific commands, no examples of sorting parameter patterns, no API snippets—nothing actionable whatsoever. It only describes what it claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to detailed materials, no links to related files, and no meaningful structural organization beyond generic headings. | 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
c8a915c
- 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.