Judge whether an API spec draft or generated workbook is trustworthy and evidence-backed. Use when running approval or postcheck gates for API design documents, checking whether parameter hierarchy, required flags, API IDs, sequence contracts, DB/table references, and workbook cells remain faithful to source code evidence and deterministic config artifacts.
Use this skill to judge trustworthiness only. Focus on whether the document can be believed, not whether it reads elegantly.
references/constitution.md.references/trust-rubric.md.approval: inspect analysis.json, api_config.json, quality_report.json, glossary evidence, and source references.postcheck: inspect the generated workbook, workbook snapshot, workbook_validation.json, and compare against api_config.json.repairable=false unless a deterministic config rewrite can fix it.Return JSON with:
status: pass|review|failblocking: booleansummary: short text or objectfindings: array of objects with severity, code, message, path, repairable