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
Quality
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 fails on all dimensions by providing only a skill name and category without explaining what the skill does, when to use it, or including any natural trigger terms. The repeated trigger term suggests auto-generated or incomplete content.
Suggestions
Add specific actions the skill performs, e.g., 'Parses and validates sorting parameters from API query strings, handles multi-field sorting, and generates SQL ORDER BY clauses'
Include a 'Use when...' clause with natural trigger terms like 'sort API results', 'order by', 'ascending/descending', 'query parameter sorting', 'paginated results ordering'
Differentiate from other API skills by specifying the exact scope, e.g., 'Specifically handles ?sort=field:asc,field2:desc style parameters in REST APIs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Sorting Parameter Handler') and mentions 'API Development' but provides no concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'parses', 'validates', 'transforms', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of functionality and no 'Use when...' clause or equivalent trigger guidance. The 'Triggers on' section just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('sorting parameter handler, sorting parameter handler'). These are not natural keywords users would say - users would more likely say 'sort API results', 'order by parameter', 'query string sorting', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'API Development' could overlap with dozens of other skills. Without specific actions or clear triggers, this could conflict with any API-related skill. Nothing distinguishes it from other parameter handling or API 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 a template placeholder with no actual content. It describes what a sorting parameter handler skill should do but provides zero concrete guidance, code examples, or implementation details. The entire content could be replaced with a single sentence: 'This skill helps with sorting parameters' without losing any information.
Suggestions
Add concrete code examples showing how to parse and validate sorting parameters (e.g., `?sort=name:asc,created_at:desc`)
Include specific patterns for common frameworks (Express, FastAPI, etc.) with executable code snippets
Provide a clear workflow: 1) Parse sort parameter, 2) Validate allowed fields, 3) Build query, 4) Handle errors
Add examples of input/output showing valid and invalid sorting parameter formats with expected responses
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information about sorting parameter handling. | 1 / 3 |
Actionability | No executable code, no concrete commands, no specific examples. The content only describes what it could do rather than providing any actual implementation guidance for sorting parameters. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for implementing sorting parameter handling. | 1 / 3 |
Progressive Disclosure | No meaningful structure or references to additional resources. The content is organized into sections but each section contains only placeholder text with no real content to disclose. | 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.