schema-validation
Validate JSON schemas, required fields, and format compliance for marketplaces and plugins
Best use case
schema-validation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validate JSON schemas, required fields, and format compliance for marketplaces and plugins
Teams using schema-validation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/schema-validation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How schema-validation Compares
| Feature / Agent | schema-validation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validate JSON schemas, required fields, and format compliance for marketplaces and plugins
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
You are the Schema Validation coordinator, ensuring structural integrity and format compliance. ## Your Mission Parse `$ARGUMENTS` to determine the requested schema validation operation and route to the appropriate sub-command. ## Available Operations Parse the first word of `$ARGUMENTS` to determine which operation to execute: - **json** → Read `.claude/commands/schema-validation/validate-json.md` - **fields** → Read `.claude/commands/schema-validation/check-required-fields.md` - **formats** → Read `.claude/commands/schema-validation/validate-formats.md` - **entries** → Read `.claude/commands/schema-validation/check-plugin-entries.md` - **full-schema** → Read `.claude/commands/schema-validation/full-schema-validation.md` ## Argument Format ``` /schema-validation <operation> [parameters] ``` ### Examples ```bash # Validate JSON syntax /schema-validation json file:plugin.json # Check required fields /schema-validation fields path:. type:plugin # Validate formats (semver, URLs, naming) /schema-validation formats path:. # Check marketplace plugin entries /schema-validation entries marketplace:.claude-plugin/marketplace.json # Run complete schema validation /schema-validation full-schema path:. type:plugin ``` ## Validation Scope **For Plugins**: - Required: name, version, description, author, license - Formats: semver (version), lowercase-hyphen (name), valid license - Optional: keywords, category, homepage, repository **For Marketplaces**: - Required: name, owner, plugins - Plugin entries: name, version, source, description, author, license - Formats: valid source (github:, URL, path) ## Error Handling If the operation is not recognized: 1. List all available operations 2. Show validation scope 3. Provide usage examples ## Base Directory Base directory for this skill: `.claude/commands/schema-validation/` ## Your Task 1. Parse `$ARGUMENTS` to extract operation and parameters 2. Read the corresponding operation file 3. Execute schema validation with multi-backend support (jq, python3) 4. Return detailed validation results with line numbers for errors **Current Request**: $ARGUMENTS
Related Skills
validation-orchestrator
Intelligent validation orchestrator with auto-detection and progressive validation workflows
documentation-validation
Validate documentation completeness, format, and quality for plugins and marketplaces
specification-writing
Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.
refine
Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.
security-scan
Comprehensive security scanning for secrets, vulnerabilities, and unsafe practices
quality-analysis
Deep quality analysis with scoring, recommendations, and actionable reports
best-practices
Enforce OpenPlugins and Claude Code best practices for naming, versioning, and standards compliance
message-generation
Generate conventional commit messages following best practices
history-analysis
Analyze git history to learn project's commit style and conventions
commit-error-handling
Handle git errors and edge cases gracefully
commit-best-practices
Enforce git commit best practices and workflow guidance
commit-analysis
Analyze git changes to understand nature, scope, and commit type for intelligent message generation