Validate outputs against required schemas using validate.sh before committing.
npx skills add https://github.com/Clouder0/dotagent --skill verify-output
Please help me install this Agent Skill. Skill: verify-output Source: https://github.com/Clouder0/dotagent/tree/main/.claude/skills/verify-output Command: npx skills add https://github.com/Clouder0/dotagent --skill verify-output
Pattern for verifying your output matches required schema before completing.
Validate the output against the relevant schema, then commit if valid.
High-intent search queries and answers about installing and using this skill.
Schema validation ensures your JSON output conforms to required structures before completion. Use the validate.sh utility to check final outputs against your schema, confirming all mandatory fields exist and have correct data types before writing.
Pre-write validation catches schema mismatches early by validating temporary outputs before finalizing. This prevents malformed JSON from entering production and ensures data integrity across demand, design, task-output, verification, reflection, and contract artifacts.
Yes, the verify-output pattern supports multiple schemas. You can validate different structured JSON outputs—such as task outputs, verification records, and contracts—each against their own required schema using the validate.sh utility.
Validation is essential for production JSON outputs and structured artifacts like demand, design, task-output, verification, reflection, evolution-proposal, and contract data. Pre-write checks via validate.sh ensure final data integrity and prevent schema violations.
Failed validation flags mandatory field gaps or incorrect data types before output is finalized. This prevents invalid data from being committed and allows you to correct the output structure before completion.
AgentientDefine MCP tool schemas with Pydantic models and strict validation.
pradyumnasagarAutomate inter-skill data transfer and provenance capture via JSON Material Passports.
cas-bigdatalabValidate structured data against JSON schemas with field and constraint checks.
RichardGeorgeDavisAnalyze TypeScript changes for typing accuracy, runtime behavior, and contract adherence.
