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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill request-validator-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining what the skill actually does, what technologies or frameworks it supports, or when Claude should choose it over other backend development skills.
Suggestions
Add specific capabilities: describe what types of validators are generated (e.g., 'Generates input validation schemas for REST APIs, validates request bodies, query parameters, and headers using Zod/Joi/JSON Schema')
Include a 'Use when...' clause with natural trigger terms: 'Use when the user needs to validate API requests, sanitize input data, create validation middleware, or mentions terms like input validation, request schema, or data sanitization'
Remove the redundant trigger term and add varied natural language triggers users would actually say when needing this functionality
| 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 itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('request validator generator' repeated twice) and overly technical. Missing natural user phrases like 'validate input', 'check request data', 'API validation', 'input sanitization', or 'schema validation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Request Validator Generator' is somewhat specific to a niche (input validation), the lack of detail means it could overlap with general backend skills, API development skills, or schema generation tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what a request validator generator skill would do in abstract terms 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 generate request validators in at least one language (e.g., Node.js with Joi/Zod, Python with Pydantic)
Define a clear workflow: 1) Analyze request schema 2) Generate validator code 3) Validate output 4) Integrate with route handler
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific patterns and anti-patterns for request validation
Include example input (API endpoint specification) and expected output (generated validator code) to make the skill actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands and add no value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual implementation details. The skill describes what it does abstractly but never shows how to actually generate request validators. | 1 / 3 |
Workflow Clarity | No workflow is defined. The content mentions 'step-by-step guidance' but provides none. There are no steps, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples file, and no actual technical content to organize or disclose progressively. | 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.