Agent skill

Automation Audit Ops

by affaan-m in affaan-m/ECC

Evidence-first automation inventory and overlap audit workflow for ECC.

MITAuto-check passedAgent Workflows

Install Automation Audit Ops

skills CLI
$ npx skills add affaan-m/ECC --skill automation-audit-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC automation-audit-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/automation-audit-ops .claude/skills/automation-audit-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
automation-audit-ops
GitHub stars
277k
Used in
2 other repos
Token cost
~1k tokens
SKILL.md length
518 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Evidence-first automation inventory and overlap audit workflow for ECC.

  • Works in 4 steps: Inventory the real surface → Classify each item by live state → Trace the proof path → …
  • The user wants to know which jobs
  • SKILL.md covers Skill Stack, When to Use, Guardrails and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Automation Audit Ops is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • The user wants to know which jobs
  • Wrappers are live
  • Missing before fixing anything

Example prompts

  • “/automation-audit-ops”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Automation Audit Ops loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 518 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 518 words, ~1,042 tokens.

Download SKILL.mdSave it as .claude/skills/automation-audit-ops/SKILL.md (or your agent's skills folder).
name
automation-audit-ops
description
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.
metadata.origin
ECC

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
Show full SKILL.md (194 more words)Show less
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

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/automation-audit-ops of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Automation Audit Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Automation Audit Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Automation Audit Ops this skillaffaan-m/ECC277k2 repos~1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from affaan-m/ECC

All 682 skills in this repo
  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed
  • Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes
  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed
  • Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Categories

Questions about Automation Audit Ops

What does Automation Audit Ops do?

Evidence-first automation inventory and overlap audit workflow for ECC. Automation Audit Ops is an agent skill from affaan-m/ECC. Evidence-first automation inventory and overlap audit workflow for ECC.

When should I use Automation Audit Ops?

Automation Audit Ops fits situations like: the user wants to know which jobs; wrappers are live; missing before fixing anything.

How do I install Automation Audit Ops in Claude Code?

Run `npx skills add affaan-m/ECC --skill automation-audit-ops -a claude-code`. Or copy the skill folder (skills/automation-audit-ops in affaan-m/ECC) into .claude/skills/automation-audit-ops in your project. Claude Code loads it when a task matches its description.

How do I install Automation Audit Ops in Codex?

Run `npx skills add affaan-m/ECC --skill automation-audit-ops -a codex`. Or copy the skill folder (skills/automation-audit-ops in affaan-m/ECC) into .agents/skills/automation-audit-ops in your project. Codex loads it when a task matches its description.

Can I use Automation Audit Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill automation-audit-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automation-audit-ops, .gemini/skills/automation-audit-ops, .github/skills/automation-audit-ops and .opencode/skills/automation-audit-ops in your project.

What does Automation Audit Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: Automation Audit Ops is instructions for the agent only.

Does Automation Audit Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Automation Audit Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Automation Audit Ops use?

Automation Audit Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Automation Audit Ops use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Automation Audit Ops?

Skills that share tags, products or a category with Automation Audit Ops: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Automation Audit Ops?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.