plugin-validator
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill plugin-validatorValidate automatically validates AI assistant code plugin structure, schemas, and compliance when user mentions validate plugin, check plugin, or plugin errors. runs comprehensive validation specific to AI assistant-code-plugins repository standards. Use when validating configurations or code. Trigger with phrases like 'validate', 'check', or 'verify'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
22%This skill is a generic template with no actual content about plugin validation. It lacks any specific commands, validation schemas, error patterns, or concrete guidance that would make it useful for validating AI assistant code plugins. The description promises comprehensive validation but the body delivers only placeholder text.
Suggestions
Add specific validation commands (e.g., `python scripts/validate_plugin.py <plugin_dir>`) with expected output examples
Include the actual plugin schema requirements or reference the specific schema file that plugins must conform to
Provide concrete examples of common validation errors and how to fix them inline, not just as external references
Define what 'trigger conditions' actually means - list the specific phrases or contexts that should invoke this validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but in a hollow way - it's generic boilerplate rather than lean, purposeful content. It doesn't waste tokens explaining concepts Claude knows, but it also doesn't provide any actual substance. | 2 / 3 |
Actionability | Completely vague and abstract with no concrete code, commands, or specific guidance. Instructions like 'Invoke this skill when trigger conditions are met' and 'Provide necessary context' are meaningless without specifics about what validation actually involves. | 1 / 3 |
Workflow Clarity | The 4-step process is generic placeholder text with no actual validation workflow. For a plugin validator, there should be specific validation commands, schema checks, and error recovery steps - none are present. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so empty that the references feel like deflection rather than appropriate content splitting. The {baseDir} placeholder suggests incomplete templating. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%This description has strong completeness with explicit 'Use when' and trigger phrases, and good trigger term coverage. However, it suffers from moderate specificity (lacking concrete action details) and potential conflict risk due to overly generic trigger terms like 'validate' and 'check' that could match many other skills.
Suggestions
Add more specific concrete actions like 'validates manifest.json structure, checks schema definitions, verifies plugin dependencies' to improve specificity
Narrow the trigger terms to be more distinctive - instead of generic 'validate' or 'check', emphasize plugin-specific triggers like 'validate plugin manifest', 'check plugin schema', 'AI assistant plugin errors'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI assistant code plugin) and some actions (validates structure, schemas, compliance), but 'runs comprehensive validation' is vague and doesn't list specific concrete actions like 'check manifest files, verify schema types, validate dependencies'. | 2 / 3 |
Completeness | Clearly answers both what (validates plugin structure, schemas, compliance for AI assistant-code-plugins repository) and when (explicit 'Use when validating configurations or code' plus 'Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms: 'validate plugin', 'check plugin', 'plugin errors', 'validate', 'check', 'verify', and 'validating configurations'. These are terms users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | While 'AI assistant-code-plugins repository standards' is specific, the generic triggers 'validate', 'check', 'verify' and 'validating configurations or code' could easily conflict with other validation-related skills. The niche is somewhat clear but triggers are too broad. | 2 / 3 |
Total | 10 / 12 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.