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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sorting-parameter-handlerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill does, how it works, or when it should be used. This would be nearly impossible for Claude to correctly select from a pool of skills.
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', 'sortBy', 'orderBy'
Distinguish from other API skills by specifying the exact scope, e.g., 'Specifically handles sort/order parameters in REST APIs, not pagination or filtering parameters'
| 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 guidance. Only category metadata is provided. | 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 too vague to be distinctive. 'API Development' is a broad category, and without specific actions or triggers, this could conflict with any API-related skill. Nothing distinguishes sorting parameters from other API parameter handling. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what a sorting parameter handler skill would do but provides zero concrete implementation guidance, code examples, or actionable steps. The entire content could be replaced with actual sorting parameter handling patterns (query string parsing, field validation, direction handling, multi-field sorting) to be useful.
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
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual implementation guidance
| 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 | There is zero concrete guidance - no code, no commands, no specific examples of how to actually implement sorting parameter handling. The content only describes what the skill claims to do, not how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for implementing sorting parameters in an API. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. References to 'Related Skills' and tags exist but point nowhere useful. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.