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
Quality
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 with no substantive content. It only provides the skill name, a redundant trigger list, and a generic category label. The description completely fails to explain what the skill does, what specific capabilities it provides, or when it should be selected over other skills.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Constructs filter expressions for REST APIs, builds query string parameters, generates WHERE clauses for database queries'
Replace the redundant trigger terms with natural user phrases like 'filter', 'query parameters', 'search filters', 'API query', 'filter syntax', 'query builder'
Add an explicit 'Use when...' clause such as 'Use when the user needs to build filtering logic for APIs, construct query parameters, or create search/filter expressions for data retrieval'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Filtering Query Builder') and mentions 'API Development' but provides no concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'builds', 'generates', 'constructs', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a circular reference to the skill name. There's no explicit guidance on when Claude should select this skill or what user requests would trigger it. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('filtering query builder, filtering query builder'). This is redundant and misses natural variations users might say like 'filter', 'query params', 'search parameters', 'API filters', 'build query', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The vague 'API Development' category and lack of specific capabilities means this could conflict with any other API-related skill. Without concrete actions or distinct triggers, Claude cannot reliably distinguish when to use this versus other 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 content is essentially a placeholder template with no actual instructional value. It describes what a filtering query builder skill should do but provides zero concrete guidance, code examples, or actionable steps. The content fails on all dimensions by being verbose yet empty of substance.
Suggestions
Add concrete, executable code examples showing how to build filtering queries (e.g., SQL WHERE clause builders, ORM query filters, or GraphQL filter arguments)
Include specific patterns for common filtering scenarios: equality, range, contains, null checks, and compound filters with AND/OR logic
Provide a clear workflow for building filters: 1) Parse filter parameters, 2) Validate inputs, 3) Build query, 4) Execute with parameterized values to prevent injection
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') 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 examples, no specific commands, and no actual instructions on how to build filtering queries. The content only describes what the skill supposedly does without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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.