Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers…
Automation Audit Ops Use this when the user asks what automations are live, which jobs are broken, where overlap exists, or what tooling and connectors are actually doing useful work right now. This is an audit-first operator skill. The job is to produce an evidence-backed inventory and a keep / merge / cut / fix-next recommendation set before rewriting anything. Skill Stack Pull these ECC-native skills into the workflow when relevant: workspace-surface-audit for connector, MCP, hook, and app inventory knowledge-ops when the audit needs to reconcile live repo truth with durable context github-ops when the answer depends on CI, scheduled workflows, issues, or PR automation ecc-tools-cost-audit when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app repo research-ops when local inventory must be compared against current platform support or public docs verification-loop for proving post-fix state instead of relying on assumed recovery When to Use
don't have the plugin yet? install it then click "run inline in claude" again.