Automation Audit Ops

You've built up a tangle of cron jobs, GitHub Actions, MCP servers, hooks, and wrapper scripts, and now you're not sure what's actually running, what's broken, or what's doing the same job twice. This is the audit-first skill that inventories all of it before you touch anything. It classifies each piece by live state (configured, authenticated, recently verified, stale, or missing), traces concrete proof for every claim, then hands you a keep/merge/cut/fix-next recommendation set. The real value is collapsing noisy automation into one canonical ECC lane instead of preserving every historical path. It won't fix things unless you ask, but it will tell you exactly what's worth keeping and what's just burning cycles.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill automation-audit-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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