request-body-validator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill request-body-validatorRequest Body Validator - Auto-activating skill for API Development. Triggers on: request body validator, request body validator Part of the API Development skill category.
Overall
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 repeats the skill name as trigger terms, lacks any description of concrete capabilities, and provides no guidance on when Claude should select this skill. The description would be nearly useless in a collection of 10+ skills.
Suggestions
Add specific actions the skill performs, e.g., 'Validates API request bodies against JSON schemas, checks required fields, validates data types, and reports validation errors with field-level details.'
Replace the redundant trigger terms with natural variations users would say: 'validate request', 'check payload', 'API validation', 'JSON schema', 'request data validation', 'body validation'.
Add an explicit 'Use when...' clause: 'Use when building or debugging APIs, validating incoming request data, or when the user mentions request validation, payload checking, or schema compliance.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Request Body Validator') without describing any concrete actions. There are no specific capabilities listed like 'validates JSON schemas', 'checks required fields', or 'reports validation errors'. | 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 body validator' repeated twice) and overly specific/technical. Missing natural variations users would say like 'validate payload', 'check request data', 'API validation', 'JSON validation', or 'schema validation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Request Body Validator' is somewhat specific to API development context, which provides some distinctiveness. However, the lack of detail about what kind of validation or which formats it handles could cause overlap with other API or validation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what a request body validator skill should do but provides zero actual implementation guidance, code examples, validation schemas, or concrete instructions. The entire content could be replaced with a single sentence without losing any information.
Suggestions
Add concrete code examples showing request body validation using common libraries (e.g., Zod, Joi, JSON Schema, Pydantic) with executable, copy-paste ready snippets
Include specific validation patterns: required fields, type checking, nested objects, arrays, custom validators, and error message formatting
Provide example request body schemas and their corresponding validation code for common API patterns (user registration, payment processing, etc.)
Add a workflow section showing how to integrate validation into API endpoints with proper error handling and response formatting
| 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 zero actionable information. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever - no code examples, no validation schemas, no specific commands or patterns. The skill describes what it claims to do but never actually instructs how to validate request bodies. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation steps, no sequences, and no actual process for request body validation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no structure pointing to detailed materials. No references to schemas, examples, or related documentation are provided. | 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.