automation-audit-ops
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 are live, broken, redundant, or missing before fixing anything.
npx skills add mturac/everything-openai-codex --skill automation-audit-ops --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 - user asks "what automations do I have", "what is live", "what is broken", or "what overlaps" - the task spans cron jobs, GitHub Actions, local hooks, MCP servers, connectors,
- Skill Stack
- When to Use
- Guardrails
- Workflow
- 1. Inventory the real surface
- 2. Classify each item by live state
- 3. Trace the proof path
- 4. End with keep / merge / cut / fix-next
- Output Format
- Pitfalls
- Verification
What does the automation-audit-ops skill do?
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 are live, broken, redundant, or missing before fixing anything.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill automation-audit-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.