request-validator-generator
Request Validator Generator - Auto-activating skill for Backend Development. Triggers on: request validator generator, request validator generator Part of the Backend Development skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
0.99xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/request-validator-generator/SKILL.mdQuality
Discovery
7%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 repeats the skill name as trigger terms, provides no concrete actions or capabilities, and lacks any guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple backend development options.
Suggestions
Add specific concrete actions like 'Generates input validation schemas, creates request body validators, validates API parameters, produces middleware for request sanitization'
Replace the duplicate trigger terms with natural user phrases like 'validate request', 'input validation', 'API schema', 'request body check', 'sanitize input'
Add an explicit 'Use when...' clause such as 'Use when the user needs to validate API requests, create input schemas, or generate validation middleware for backend services'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Request Validator Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates validation schemas', 'validates input types', or 'creates middleware'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('request validator generator, request validator generator'). No natural user language like 'validate input', 'check request body', 'API validation', or 'schema validation' is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Request Validator Generator' is somewhat specific to a niche (validation in backend development), the lack of detail means it could overlap with general backend skills, API skills, or schema generation skills without clear differentiation. | 2 / 3 |
Total | 5 / 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 with no actual instructional value. It describes a 'request validator generator' capability in purely abstract terms without providing any concrete code, examples, patterns, or actionable guidance. The content tells Claude what the skill is supposed to do but never shows how to do it.
Suggestions
Add concrete, executable code examples showing how to generate request validators in at least one language (Node.js, Python, or Go)
Define a clear workflow: input schema format → validation rules → generated validator code → testing/verification steps
Include specific examples of input (e.g., an API request schema) and expected output (e.g., generated validator code)
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual implementation details. The skill describes what it does in abstract terms but never shows how to actually generate request validators. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The content only describes when the skill activates, not what actions to take. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no structure for discovery. There are no references to detailed materials, no examples to follow, and no organization beyond generic section headers. | 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
994edc4
- 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.