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. Pull these ECC-native skills into the workflow when relevant: Read the current live surface before theorizing: Group them by surface: For every surfaced automation, mark: Then classify the problem type: Back every important claim with a concrete source: If the current state is ambiguous, say so directly instead of pretending the audit is complete. For each overlapping or suspect surface, return one call: The value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path. - 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...