input-validation-checker
Input Validation Checker - Auto-activating skill for Security Fundamentals. Triggers on: input validation checker, input validation checker Part of the Security Fundamentals skill category.
Overall
score
20%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill input-validation-checkerActivation
0%This description is severely lacking across all dimensions. It reads like auto-generated boilerplate with no actual content describing what the skill does or when to use it. The repeated trigger term and absence of concrete actions make it nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Validates user inputs for SQL injection, XSS attacks, and malformed data. Checks form fields, API parameters, and query strings for security vulnerabilities.'
Include a 'Use when...' clause with natural trigger terms like 'validate input', 'check for injection', 'sanitize user data', 'security review of forms', 'input sanitization'.
Remove the duplicate trigger term and replace with varied, natural keywords users would actually say when needing input validation help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Input Validation Checker') without describing any concrete actions. There are no specific capabilities listed like 'validates user inputs', 'checks for SQL injection', or 'sanitizes form data'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states it's an 'auto-activating skill' in a category, with no explicit triggers or use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('input validation checker, input validation checker'). No natural user keywords like 'sanitize', 'validate input', 'security check', 'XSS', 'injection', or 'user input' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Security Fundamentals' could overlap with many security-related skills. Without specific capabilities or triggers, it's impossible to distinguish from other security skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%This skill is essentially a placeholder with no actual content. It describes what an input validation checker skill might do but provides zero actionable guidance, no code examples, no validation patterns, and no concrete security techniques. The entire content could be replaced with actual input validation examples (SQL injection prevention, XSS filtering, type checking) in fewer tokens.
Suggestions
Add concrete, executable code examples for common input validation scenarios (e.g., sanitizing user input, validating email formats, preventing SQL injection)
Include specific validation patterns with before/after examples showing vulnerable vs. secure code
Define a clear workflow for implementing input validation: identify inputs → classify risk → apply appropriate validation → test with malicious inputs
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual validation techniques and OWASP references
| 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 actionable content. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific validation techniques, no commands, no actual input validation patterns. The skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. For a security-related skill involving input validation, the complete absence of validation checkpoints or processes is a critical gap. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with clear sections, but there are no references to detailed materials, no links to examples or advanced content, and the sections themselves contain no substantive information to disclose. | 2 / 3 |
Total | 5 / 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.