filtering-query-builder
Filtering Query Builder - Auto-activating skill for API Development. Triggers on: filtering query builder, filtering query builder Part of the API Development skill category.
34
0%
Does it follow best practices?
Impact
98%
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/filtering-query-builder/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 that repeats the skill name without providing any substantive information about what the skill does, what concrete actions it performs, or when it should be selected. It lacks specific capabilities, natural trigger terms, explicit usage guidance, and distinguishing details that would allow Claude to correctly select it from a pool of skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Constructs filter query strings for REST APIs, builds WHERE clauses, generates query parameter objects for search/filter endpoints.'
Add an explicit 'Use when...' clause with natural trigger terms like 'filter API results', 'query parameters', 'search endpoint', 'build filters', 'query builder', 'API filtering'.
Differentiate from related skills by specifying the exact type of filtering (e.g., REST API query parameters vs. database queries vs. GraphQL filters) and the output format or framework involved.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('API Development') and a concept ('Filtering Query Builder') but describes no concrete actions. There are no verbs indicating what the skill actually does—no 'builds', 'generates', 'constructs queries', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name and provides no meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'filtering query builder' repeated twice. There are no natural user keywords like 'filter', 'query parameters', 'search API', 'WHERE clause', 'query string', or other variations a user might naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other API-related skills. 'Filtering Query Builder' could overlap with database query skills, search skills, ORM skills, or general API development skills without any clear differentiating details. | 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 only generic boilerplate descriptions that provide no actionable guidance on filtering query builders, no code examples, no API patterns, and no real information. It fails on every dimension because it teaches Claude nothing it doesn't already know and provides nothing concrete to act on.
Suggestions
Add concrete, executable code examples showing how to build filtering queries for REST and GraphQL APIs (e.g., query parameter parsing, filter object construction, SQL/ORM query generation).
Define a clear workflow for building a filtering system: e.g., 1) Parse filter parameters, 2) Validate filter fields against schema, 3) Build query, 4) Execute with sanitized inputs—with validation checkpoints.
Include specific patterns and anti-patterns for common filtering scenarios (e.g., comparison operators, logical combinators, nested filters, pagination integration).
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with domain-specific content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information about filtering query builders, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific commands, no API patterns, no query builder syntax, no executable content whatsoever. It only describes what the skill would do in abstract terms. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 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. No bundle files exist to support it 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.