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 with no substantive 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 it. It would be nearly impossible for Claude to reliably choose this skill from a pool of similar backend development skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates input validation logic for API endpoints, creates schema validators for request bodies, query parameters, and headers using libraries like Joi, Zod, or express-validator.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to validate API requests, create input validation middleware, generate request schemas, or sanitize user input in backend services.'
Remove the duplicated trigger term and replace with diverse natural keywords users would actually say, such as 'validate request', 'input validation', 'request schema', 'API validation', 'sanitize input', 'validation middleware'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('request validator generator') but provides no concrete actions. It does not explain 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. | 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 input', 'request schema', 'input validation', 'sanitize', 'middleware', or 'API validation'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Backend Development' category and a repeated skill name provide no clear niche. It could easily conflict with any validation, schema generation, or backend development skill. | 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 actual instructional content. It repeatedly references 'request validator generator' without ever defining what a request validator is, how to generate one, or providing any code, commands, schemas, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for generating request validators in at least one language (e.g., Zod schemas for Node.js, Pydantic models for Python, or struct tags for Go).
Define a clear workflow: e.g., 1) Identify request fields and types, 2) Generate validator code, 3) Validate against test payloads, 4) Integrate into route handler—with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actionable technical content.
Add references to separate files for language-specific validator patterns (e.g., 'See [NODE_VALIDATORS.md](NODE_VALIDATORS.md) for Express/Zod patterns') 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 information about 'request validator generator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no schemas, no examples of validators, no library recommendations. The content only 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 contains none. There are no validation checkpoints or sequenced instructions of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered content organization, and the sections are superficial headers over near-identical boilerplate text. | 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.