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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill filtering-query-builderOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It fails on all dimensions by providing only the skill name, a redundant trigger, and a generic category label. Claude would have no basis for selecting this skill appropriately from a skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Constructs filter expressions for REST APIs, builds query parameters for pagination, sorting, and field filtering'
Include a 'Use when...' clause with natural trigger terms like 'filter API results', 'query parameters', 'search endpoint', 'pagination', 'sort by', 'where clause'
Specify the types of queries or APIs supported (REST, GraphQL, OData) to distinguish from other API development skills
| 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' (no actions described) and 'when should Claude use it' (no use cases or scenarios). The 'Triggers on' section just repeats the skill name without meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'filtering query builder' repeated twice, which is the skill name itself. Missing natural user terms like 'filter', 'query', 'search parameters', 'API filters', 'where clause', 'query string', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'API Development' is a broad category that could overlap with many skills. Without specific capabilities or triggers, Claude cannot distinguish when to use this over other API-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive technical guidance. It describes what a filtering query builder skill should do but provides absolutely no actionable content, code examples, or concrete instructions. The entire body consists of generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable code examples showing how to build filtering queries (e.g., SQL WHERE clause builders, ORM query filters, 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 type-safe filter queries with validation steps
Replace generic capability claims with actual implementation guidance and API-specific examples (REST query params, GraphQL filter inputs)
| 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. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for any filtering query builder task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure pointing to detailed materials, no references to implementation guides, and no organized navigation to actual technical content. | 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.