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.
34
0%
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
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 meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, explicit usage guidance, and distinctive characteristics that would allow Claude to correctly select it from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates request validation middleware, creates input schemas, validates request bodies, query parameters, and headers for API endpoints.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to validate API requests, create input validation, generate request schemas, add middleware for request checking, or mentions terms like validate, sanitize, request body, query params.'
Remove the duplicate trigger term and replace with varied natural keywords users would actually say, such as 'input validation', 'request schema', 'API validation', 'sanitize input', 'validation middleware', 'Joi', 'Zod', 'express-validator'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('request validator generator') but provides no concrete actions. It does not describe what the skill actually does—no mention of generating validation schemas, checking request bodies, validating parameters, etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explicit 'Use when...' clause and no meaningful explanation of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('request validator generator, request validator generator'). There are no natural user keywords like 'validate request', 'input validation', 'schema validation', 'request body', 'API validation', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinguishable. 'Backend Development' is extremely broad, and without specific actions or triggers, it could easily conflict with any backend-related skill involving validation, schemas, or request handling. | 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 repeatedly references 'request validator generator' without ever explaining what one is, how to build one, or providing any code, commands, or concrete guidance. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples for generating request validators in at least one language (e.g., a Zod schema in Node.js, a Pydantic model in Python, or a struct with validation tags in Go).
Define a clear workflow: e.g., 1) Identify request fields and types, 2) Generate validator schema, 3) Integrate middleware, 4) Validate with test cases — with explicit validation checkpoints.
Remove all boilerplate meta-text (Purpose, When to Use, Example Triggers sections) and replace with actual technical content that teaches Claude how to generate request validators.
If the skill covers multiple languages/frameworks, create separate reference files (e.g., NODE_VALIDATORS.md, PYTHON_VALIDATORS.md) and link to them from a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'request validator generator' excessively, and provides zero substantive information about how to actually generate request validators. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no actual guidance on generating request validators. The content is purely descriptive meta-text about the skill itself rather than actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow steps, no sequence, no validation checkpoints are provided. The phrase 'step-by-step guidance' is mentioned as a capability but never delivered. | 1 / 3 |
Progressive Disclosure | No references to supporting files, no structured navigation, and no content organization beyond generic boilerplate headings. There are no bundle files and the content itself is a monolithic block of non-information. | 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
13d35b8
- 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.