Skip to main content
Agent skill

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.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Automation Audit Ops when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Automation Audit Ops when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/automation-audit-ops
# Save SKILL.md to ~/.claude/skills/automation-audit-ops/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/automation-audit-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/automation-audit-ops/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Automation Audit Ops skill for this task: user asks "what automations do I have", "what is live", "what is broken", or "what overlaps". Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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, wrappers, or app integrations - the user wants to know what was ported from another agent system and what still needs to be rebuilt inside ECC - the workspace has accumulated multiple ways to do the same thing and the user wants one canonical lane

## Guardrails

- start read-only unless the user explicitly asked for fixes - separate: - configured - authenticated - recently verified - stale or broken - missing entirely - do not claim a tool is live just because a skill or config references it - do not merge or delete overlapping surfaces until the evidence table exists

## Workflow

### 1. Inventory the real surface

Read the current live surface before theorizing:

- repo hooks and local hook scripts - GitHub Actions and scheduled workflows - MCP configs and enabled servers - connector- or app-backed integrations - wrapper scripts and repo-specific automation entrypoints

Group them by surface:

- local runtime - repo CI / automation - connected external systems - messaging / notifications - billing / customer operations - research / monitoring

### 2. Classify each item by live state

For every surfaced automation, mark:

- configured - authenticated - recently verified - stale or broken - missing

Then classify the problem type:

- active breakage - auth outage - stale status - overlap or redundancy - missing capability

### 3. Trace the proof path

Back every important claim with a concrete source:

- file path - workflow run - hook log - config entry - recent command output - exact failure signature

If the current state is ambiguous, say so directly instead of pretending the audit is complete.

### 4. End with keep / merge / cut / fix-next

For each overlapping or suspect surface, return one call:

- keep - merge - cut - fix next

The value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.

## Output Format

```text CURRENT SURFACE - automation - source - live state - proof

FINDINGS - active breakage - overlap - stale status - missing capability

RECOMMENDATION - keep - merge - cut - fix next

NEXT ECC MOVE - exact skill / hook / workflow / app lane to strengthen ```

## Pitfalls

- do not answer from memory when the live inventory can be read - do not treat "present in config" as "working" - do not fix lower-value redundancy before naming the broken high-signal path - do not widen the task into a repo rewrite if the user asked for inventory first

## Verification

- important claims cite a live proof path - each surfaced automation is labeled with a clear live-state category - the final recommendation distinguishes keep / merge / cut / fix-next

Intended uses

  • 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, wrappers, or app integrations
  • the user wants to know what was ported from another agent system and what still needs to be rebuilt inside ECC
  • the workspace has accumulated multiple ways to do the same thing and the user wants one canonical lane

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.