feature-dashboard

You can audit skill connectivity across eight layers by validating metadata, orchestrator presence, contract YAML, event bus configuration, and test coverage. It reports integration gaps by flagging skills as broken, partial, or wired in machine-readable JSON or human-readable formats.

Skill connectivity auditing is the process of validating system integration across layers like topic namespacing and Linear ticket linkage. You need to validate it before deployment to ensure new skills meet integration standards and avoid broken connections.

You can automatically create Linear tickets for broken integration workflows by running the audit in ticketize mode. This mode identifies connectivity gaps and directly generates tickets for the responsible teams to fix the issues.

Yes, you can export system integration audit results to Markdown or HTML. The audit supports configurable output formats including machine-readable JSON, CLI output, and human-readable Markdown and HTML for analysis and reporting.

Yes, the connectivity audit explicitly checks event bus configuration and contract YAML files. It validates these layers alongside skill metadata, orchestrator presence, topic definitions, and test coverage to identify partial or broken integrations.

Automated skill connectivity audits are limited to read-only analysis unless explicitly run in ticketize mode. They validate static configuration layers like contract YAML and event bus topics but do not execute runtime integration tests or modify the existing skill architecture.