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 is an extremely weak description that appears to be auto-generated boilerplate with no meaningful content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly impossible for Claude to correctly choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Builds filtering query expressions for REST APIs, constructs query parameter strings, generates WHERE clauses for database-backed endpoints, and creates filter DSL objects.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about building API filters, constructing query parameters, creating search/filter endpoints, or writing filter expressions for REST or GraphQL APIs.'
Remove the duplicate trigger term and replace with varied natural keywords users would say, such as 'filter', 'query builder', 'search parameters', 'API query', 'filter endpoint', 'query string', 'filter DSL'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Filtering Query Builder') and mentions 'API Development' as a category, but provides no concrete actions like building filter expressions, constructing query parameters, or generating WHERE clauses. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a redundant repetition of the skill name. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('filtering query builder, filtering query builder'). There are no natural user keywords like 'filter', 'query', 'search parameters', 'WHERE clause', 'API filters', or similar terms users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this from other API-related skills, database query skills, or general filtering tools. 'API Development' is a broad category that could overlap with many other 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 shell with no actual instructional content. It consists entirely of meta-descriptions and trigger phrases, providing zero actionable guidance on building filtering queries for APIs. It fails on every dimension because it contains no code, no concrete patterns, no workflows, and no references to supplementary materials.
Suggestions
Add concrete, executable code examples showing how to build filtering queries (e.g., SQL WHERE clause builders, ORM query filters, GraphQL filter arguments, REST query parameter parsing).
Define a clear workflow for constructing filters: parse input parameters → validate filter fields against allowed list → build query → sanitize against injection → execute, with validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task, and replace with actual technical content.
Add references to related detailed guides (e.g., a PATTERNS.md for common filter patterns, EXAMPLES.md for different API styles) to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea—that it helps with 'filtering query builder'—without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of actual filtering query construction. The content describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but includes none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic descriptions with no references to detailed materials, no links to examples or API references, and no meaningful structural organization beyond boilerplate 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.