api-spec-gate-trust

Evaluate API documents for evidence alignment and data integrity.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/SevenThRe/web-ui-spec-upgrade-temp-20260410-085931 --skill api-spec-gate-trust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-spec-gate-trust
Source: https://github.com/SevenThRe/web-ui-spec-upgrade-temp-20260410-085931/tree/main/web-ui-spec-unpacked-20260327/skills/api-spec-gate-trust
Command: npx skills add https://github.com/SevenThRe/web-ui-spec-upgrade-temp-20260410-085931 --skill api-spec-gate-trust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Judge API design drafts or generated workbooks for trustworthiness and faithful reflection of source evidence.

Core Features & Use Cases

  • Evidence-backed validation: Checks consistency between API spec artifacts, analysis reports, and configuration.
  • Approval and Postcheck support: Applies gates during initial approval and later postcheck to catch drift.
  • Structured findings: Emits JSON-formatted findings detailing mismatches and evidence references.

Quick Start

Validate a draft against the constitution and trust rubric to confirm readiness for workbook export.

Frequently Asked Questions about api-spec-gate-trust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate API specs for trust and evidence alignment?

API spec validation evaluates documents for trustworthiness by examining analysis artifacts, configuration, and source references to ensure consistency. It enforces data integrity rules and requires structured evidence like api_config.json and analysis.json to confirm readiness.

What is API postcheck governance and when do I need it?

API postcheck governance applies trust gates after initial approval to catch configuration drift. You need it when validating generated workbooks or design drafts against a trust rubric to verify faithful reflection of source evidence before export.

How do I check API configuration mismatches against analysis reports?

Checking API configuration mismatches involves comparing api_config.json and analysis.json files against source references. The process enforces data integrity rules, forbids missing data, and emits JSON-formatted findings detailing any evidence mismatches.

Does API spec validation require specific input files to run?

API spec validation requires structured evidence files including api_config.json, analysis.json, and defined trust rubrics. Without these input artifacts, the governance gate cannot evaluate source references or enforce data integrity rules.

What happens when API spec evidence validation fails?

When API spec evidence validation fails, it emits structured JSON-formatted findings detailing specific mismatches and missing data. The gate forbids progression until configuration and analysis artifacts align with the required trust rubric.