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.
Security Assessment
About automation-audit-ops
The `automation-audit-ops` skill provides a structured, evidence-first approach to auditing automation workflows within the ECC environment. Its primary purpose is to help users identify which jobs, hooks, connectors, MCP servers, or wrapper scripts are live, broken, redundant, or missing before making any changes. By focusing on verification rather than assumption, this skill ensures that any automation modifications are grounded in accurate, current data, reducing the risk of disrupting live systems or duplicating effort.
Key features include inventorying the live automation surface, classifying each item by its operational state, tracing proof for each claim, and producing actionable recommendations. The skill leverages related ECC-native tools such as `workspace-surface-audit` for inventorying, `knowledge-ops` for reconciling live data with repository truth, and `verification-loop` for post-fix validation. The output is organized into clear sections: current surface, findings, recommendations, and next ECC moves, with classifications including active breakage, overlap, stale status, and missing capability.
This skill is particularly useful for users responsible for maintaining or optimizing complex automation systems, such as DevOps engineers, system integrators, and ECC workspace administrators. It is ideal when the user needs to assess live automations, detect redundancies, or plan a canonical path for repair or consolidation. Common use cases include evaluating automation inventory, identifying broken or overlapping jobs, verifying integration health, and preparing a prioritized action plan for fixing or merging automation lanes.
FAQ
When should I use the automation-audit-ops skill?
Use it when you need to know what automations are live, broken, or overlapping, or when you want to audit connectors, jobs, MCP servers, hooks, and wrappers before making any changes.
Which ECC-native tools does this skill integrate with?
It integrates with `workspace-surface-audit` for inventory, `knowledge-ops` for reconciling live data, `github-ops` for CI and workflow context, `ecc-tools-cost-audit` for job and webhook analysis, `research-ops` for platform support comparison, and `verification-loop` for validating post-fix states.
Does this skill make changes to automation automatically?
No, it starts in read-only mode. Fixes or merges are only suggested as recommendations based on evidence. Actual changes are not performed unless explicitly requested.
What types of issues can automation-audit-ops detect?
It can detect active breakage, authentication outages, stale status, overlapping or redundant automation, and missing capabilities across hooks, scripts, workflows, servers, and integrations.
Can it determine if a tool is truly live?
Yes, but only based on concrete evidence such as logs, config entries, workflow runs, or command outputs. It will not assume a tool is live just because it is referenced in configuration.
Install automation-audit-ops
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
affaan-m/everything-claude-code