automation-audit

To audit automations, run a validation check across the catalog to identify missing JSON schemas, docs, icons, and questions. The process outputs a coverage matrix with severity-labeled gaps to guide remediation before releases or periodic quality checks.

Catalog-wide validation checks each automation for required artifacts including catalog entries, JSON schemas, questions, docs, and icons. It tallies gaps by severity to surface inconsistencies that could affect platform reliability and deployments.

Run an automation coverage check after adding new automations, before releases, or on a recurring schedule for quality governance. It validates docs and schemas to ensure complete coverage and identify inconsistencies prior to deployment.

Yes, the audit skill is applicable for platform-wide reviews, release checks, and periodic quality audits. It reads the catalog, schemas, and questions to validate docs and icons, outputting a coverage matrix with severity-labeled gaps.

Yes, the automation audit reads the catalog, schemas, and questions to validate docs and icons. It checks each automation for catalog entry, JSON schema, questions, docs, and icon presence to ensure complete coverage.

The best way to generate a coverage matrix is to run an automation audit that reads the catalog, schemas, and questions. It validates docs and icons, then outputs a matrix with severity-labeled gaps to guide remediation.