Install command
Provided
Compile JSON Schema (draft-07, 2019-09, 2020-12) into fast validators with Ajv, report every failure by its instancePath, and use Ajv options to coerce types, apply defaults, and remove unknown properties so incoming JSON is both validated and normalized.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
6 to clear
Platforms
6 listed
Difficulty
100/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
6 prerequisites to line up before setup.
Safety & privacy surface
2 safety and 1 privacy notes across 3 risk areas. Review closely: network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
import Ajv from "ajv";
const ajv = new Ajv({ allErrors: true, strict: true });
const validate = ajv.compile({
type: "object",
properties: { id: { type: "string" } },
required: ["id"],
additionalProperties: false
});
console.log(validate({ id: "abc" })); // true
console.log(validate({})); // false, see validate.errorsClaude can validate JSON against JSON Schema with Ajv — compiling schemas, reporting failures by instancePath, and using Ajv options to coerce types, apply defaults, and remove unknown properties so data is validated and normalized in one pass. For work beyond validation, it uses companion tools: json-schema-to-typescript to generate TypeScript types from a schema, and scripted migrations that re-validate every document against the target schema.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Required:
What Claude handles:
Prompt: "Validate this JSON data against the provided JSON Schema. Show me all validation errors."
Claude will:
Prompt: "Generate TypeScript interfaces from this JSON Schema."
Claude will:
Prompt: "Transform this API response from format A to format B according to this mapping schema."
Claude will:
Prompt: "Migrate these 100 JSON documents from schema v1 to schema v2. Show me the migration script and any issues."
Claude will:
"Create a validation script that:
1. Loads this OpenAPI spec
2. Extracts the POST /users request schema
3. Validates this payload against it
4. Returns detailed error messages for invalid fields
5. Suggests corrections"
"Validate all JSON config files in the uploaded directory:
1. Check against config.schema.json
2. Report which files are invalid
3. For each error, show: file, path, expected type, actual value
4. Suggest fixes for common errors
5. Generate a validation report"
"Normalize this messy JSON data:
1. Validate against the schema
2. Fix common issues (trim strings, coerce types)
3. Remove extra properties not in schema
4. Fill in default values for missing optional fields
5. Export clean, validated JSON"
"Transform all JSON files from old format to new:
1. Load transformation rules
2. For each file:
- Parse and validate source
- Apply transformations
- Validate against target schema
- Save to output/
3. Report success/failure stats"
Issue: Schema validation too strict Solution: Ask Claude to adjust: "Allow additional properties" or "Coerce types when possible"
Issue: $ref resolution errors Solution: Either inline all schemas or ensure all referenced files are uploaded
Issue: Type coercion not working as expected Solution: Be explicit: "Convert string numbers to integers" or "Parse ISO date strings to Date objects"
Issue: Large JSON files cause memory issues Solution: "Process this file in streaming mode" or "Validate in chunks of 1000 records"
Issue: Validation errors are cryptic Solution: Ask for better errors: "Explain each validation error in plain English with examples"
Issue: Migration breaks data Solution: "Validate each step of the migration" and "Keep backup of original values for rollback"
Show that JSON Schema Validate + Transform Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/json-schema-validation-transformation)JSON Schema Validate + Transform Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Compile JSON Schema (draft-07, 2019-09, 2020-12) into fast validators with Ajv, report every failure by its instancePath, and use Ajv options to coerce types, apply defaults, and remove unknown properties so incoming JSON is both validated and normalized. Open dossier | TypeScript-first validation skill using Zod — define schemas once, get runtime checks and inferred types for APIs, forms, and data pipelines. Open dossier | Expert Claude Code computer use GUI QA capability pack that applies documented computer-use MCP enablement, per-app session approval, screenshot checkpoints, and macOS permission workflows for native app validation—not an official Anthropic QA product. Open dossier | Expert Claude Code zero data retention review capability pack for auditing ZDR scope on Claude for Enterprise, disabled features, model availability, analytics limits, and third-party integration gaps before rollout. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2025-10-15 | Package verified2025-10-16 | Package not verified | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | Submission linkedSource submission | Submission linkedSource submission |
| SubmitterDiffers | — | — | kiannidev | kiannidev |
| Install risk | Review first | Low risk | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | skills | skills | skills | skills |
| Source | first-party | first-party | source-backed | source-backed |
| Author | JSONbored | JSONbored | kiannidev | kiannidev |
| Added | 2025-10-15 | 2025-10-16 | 2026-06-16 | 2026-06-13 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓This skill installs npm packages (ajv, zod, json-schema-to-typescript) and reads and writes local files — JSON schemas, data, migration output, and generated TypeScript definitions. Ajv type coercion and default-filling mutate the input data, and migration scripts overwrite documents; keep backups and re-validate each step, as the skill's troubleshooting notes recommend. | ✓Install Zod with `npm install zod` (or your package manager's equivalent) before use. The library has zero runtime dependencies and does not execute network requests on its own. Async refinements (`.refine(async fn)`) may call external services if your own callback does — review any async refinement for unintended network or database access. | ✓Computer use controls real desktop apps with per-app session approval—not sandboxed Bash. Review sentinel warnings before approving Terminal, Finder, or System Settings access. Press Esc or Ctrl+C to stop computer use and release the machine-wide lock immediately. Only one Claude Code session can hold the computer-use lock at a time. | ✓This skill summarizes official ZDR scope; it must not claim ZDR covers chat on claude.ai, Cowork, third-party MCP servers, or Bedrock, Vertex, or Foundry routes. ZDR is enabled per organization; new organizations require separate enablement by the Anthropic account team. Disabled features such as Claude Code on the Web, Desktop cloud sessions, and `/feedback` are blocked at the backend regardless of client UI. Claude Fable 5 is unavailable under ZDR; the `best` alias resolves to Opus for ZDR organizations instead. Policy-violation sessions may still be retained for up to two years even when ZDR is enabled. |
| Privacy notes | ✓Validation, normalization, and migration process your JSON data and schema files locally; nothing leaves the machine beyond the npm package downloads from the registry. | ✓Zod validates data in-process only and does not transmit your schemas, inputs, or error output to any external service. Schemas that validate emails, passwords, or personal data remain entirely local; no input leaves your runtime environment through Zod itself. | ✓Screenshots are downscaled before model upload but may still capture sensitive UI content. Your terminal window is excluded from screenshots per official documentation. Redact customer or proprietary UI details before sharing screenshot evidence externally. Other visible apps are hidden while Claude works; still minimize sensitive windows before starting. | ✓ZDR review discussions often involve account emails, organization names, contract terms, and security architecture details that should stay in internal channels. Claude Code Analytics under ZDR does not store prompts or model responses but still collects productivity metadata such as account emails and usage statistics. Administrative data such as seat assignments and audit logs follow standard retention policies and remain in scope for compliance review. Third-party MCP servers, local logs, hooks, and customer-managed observability stacks are outside Anthropic ZDR and need separate review. |
| Prerequisites |
|
|
|
|
| Install | | | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.