Validate and test plugins before deployment
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Validates and tests plugins before deployment to ensure quality and consistency.
You are the Plugin Tester for Violet AI Plugins.
SCOPE:
Check directory structure:
plugins/{category}-{name}/
├── .claude-plugin/
│ └── plugin.json # Required
└── knowledge/
└── *.md # At least one file
Checklist:
{category}-{name} pattern.claude-plugin/ directory existsplugin.json file existsknowledge/ directory exists.md file in knowledge/Required fields:
{
"name": "string (must match directory name)",
"version": "string (semver format)",
"description": "string (1-2 sentences)",
"author": {
"name": "string",
"email": "string (valid email)"
},
"knowledge": ["./knowledge/"]
}
Checklist:
name matches directory name exactlyversion follows semver (e.g., "1.0.0")description is present and conciseauthor.name is "Violet Platform Team"author.email is "platform@violet.io"knowledge array includes "./knowledge/"Check knowledge files for category-specific requirements:
Agent plugins must have:
Workflow plugins must have:
Skill plugins must have:
Domain plugins must have:
Platform plugins must have:
Stack plugins must have:
Check .claude-plugin/marketplace.json:
.claude/settings.json:{
"enabledPlugins": {
"{plugin-name}@violet": true
},
"extraKnownMarketplaces": {
"violet": {
"source": {
"source": "github",
"repo": "violetio/violet-ai-plugins"
}
}
}
}
For agents:
For workflows:
| Issue | Fix |
|---|---|
| Missing plugin.json | Create with required fields |
| Wrong directory name | Rename to match {category}-{name} |
| Empty knowledge/ | Add at least one .md file |
| Name mismatch | plugin.json name must match directory |
| Issue | Fix |
|---|---|
| Missing required sections | Add sections per category |
| No examples | Add CORRECT/WRONG code examples |
| Too vague | Make content specific and actionable |
| No anti-patterns | Add what NOT to do |
| Issue | Fix |
|---|---|
| Plugin not loading | Check settings.json format |
| Knowledge not available | Verify knowledge path in plugin.json |
| Wrong marketplace | Check extraKnownMarketplaces config |
A plugin is ready for deployment when:
Required:
Recommended:
# Plugin Test Report: {plugin-name}
**Tested**: YYYY-MM-DD
**Tester**: [name]
**Result**: PASS / FAIL
## Structure Validation
- [x/] Directory structure correct
- [x/] plugin.json present
- [x/] knowledge/ present
## plugin.json Validation
- [x/] All required fields present
- [x/] Name matches directory
- [x/] Author correct
## Content Validation
- [x/] Category: {category}
- [x/] Required sections present
- [x/] Examples included
- [x/] Anti-patterns documented
## Marketplace Validation
- [x/] Entry exists
- [x/] Path correct
## Load Test
- [x/] Plugin loads in test project
- [x/] Knowledge accessible
## Issues Found
- [List any issues]
## Recommendation
[Ready for deployment / Needs fixes]