Harness-engineering harness-data-validation

name: harness-data-validation version: "1.0.0" description: Schema validation, data contracts, and pipeline data quality stability: static cognitive_mode: meticulous-verifier triggers:

• manual
• on_pr platforms:
• claude-code
• gemini-cli
• cursor
• codex tools:
• Bash
• Read
• Write
• Edit
• Glob
• Grep cli: command: harness skill run harness-data-validation args:
  • name: path description: Project root path required: false
  • name: library description: "Validation library: zod, yup, joi, valibot, json-schema. Auto-detected when omitted." required: false
  • name: strict description: Fail on any unvalidated boundary crossing required: false mcp: tool: run_skill input: skill: harness-data-validation path: string type: rigid tier: 3 internal: false keywords:
• validation
• schema
• Zod
• JSON Schema
• Protobuf
• Avro
• data contract
• data quality
• type safety
• runtime validation
• Valibot
• Yup
• Joi stack_signals:
• "src//schemas/"
• "src//validators/"
• "*.schema.json"
• "*.proto"
• "*.avsc"
• "src/**/.zod." phases:
• name: detect description: Identify validation libraries, schema definitions, and trust boundaries required: true
• name: audit description: Find unvalidated inputs, missing schemas, and type-runtime mismatches required: true
• name: enforce description: Generate or fix validation schemas at every trust boundary required: true
• name: verify description: Confirm all boundaries are covered and schemas match runtime types required: true state: persistent: false files: [] depends_on: [] related_skills:
• zod-schema-definition
• zod-object-patterns
• zod-error-handling
• ts-type-guards