json-schema

I've been digging into JSON Schema validation tooling lately, and I like how your skill approaches the problem—the structured breakdown of validation patterns is solid, though I'm curious about some of the edge cases your implementation handles at scale.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 82/100, solid B-grade territory. This is based on Anthropic's agentic skills best practices. Your writing style is chef's kiss (9/10)—the imperative voice and technical objectivity are exactly right—but you're leaving points on the table with Progressive Disclosure Architecture (22/30) because everything lives in one 73-line file and Utility (15/20) because there's no validation feedback loop or testing guidance.

What's Working Well

• Trigger phrases are dialed in. "JSON Schema", "OpenAPI", "validation", "type definitions"—developers searching for this stuff will find it. The metadata is doing heavy lifting.
• Writing is lean and purposeful. Every sentence in the tables earns its space. No fluff, no marketing speak. The examples like {"type": "object", "properties": {...}} are complete and actionable.
• Composition patterns section actually helps. The allOf, oneOf, anyOf breakdown is exactly what someone needs when they're stuck deciding between composition strategies.

The Big One: Missing Reference Files for Deep Topics

Here's what's holding you back from a A: you've got all your content jammed into SKILL.md with no external references for the complex stuff. When someone needs to understand advanced validation patterns, conditional schemas, or the nuances of OpenAPI 3.1 integration, there's nowhere to dig deeper.

The fix: Create a references/ directory with files like:

• references/advanced-composition.md — `all...