What it does
Evidence-first automation inventory and overlap audit workflow for ECC
Skills ZICQ category:Agent Workflows 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.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Evidence-first automation inventory and overlap audit workflow for ECC
- user asks "what automations do I have", "what is live", "what is broken", or "what overlaps"
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Automation Audit Ops; Skill Stack; When to Use; Guardrails; Workflow; 1. Inventory the real surface. It includes spec-recommended sections: step-by-step instructions.
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Automation Audit OpsSkill StackWhen to UseGuardrailsWorkflow1. Inventory the real surface2. Classify each item by live state3. Trace the proof path4. End with keep / merge / cut / fix-nextOutput FormatPitfallsVerification
Source category:skills.sh agent-skill
nameautomation-audit-opsdescriptionInvocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "automation-audit-ops" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-d5f00a726d67ca3e-Automation-Audit-Ops.html Save it as .cursor/skills/automation-audit-ops/SKILL.md or .claude/skills/automation-audit-ops/SKILL.md and keep the frontmatter name and description exactly as-is.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/affaan-m/ecc' --list
npx skills add 'https://github.com/affaan-m/ecc' --skill 'automation-audit-ops'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
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.
Pull these ECC-native skills into the workflow when relevant:
workspace-surface-audit for connector, MCP, hook, and app inventoryknowledge-ops when the audit needs to reconcile live repo truth with durable contextgithub-ops when the answer depends on CI, scheduled workflows, issues, or PR automationecc-tools-cost-audit when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app reporesearch-ops when local inventory must be compared against current platform support or public docsverification-loop for proving post-fix state instead of relying on assumed recoveryRead the current live surface before theorizing:
Group them by surface:
For every surfaced automation, mark:
Then classify the problem type:
Back every important claim with a concrete source:
If the current state is ambiguous, say so directly instead of pretending the audit is complete.
For each overlapping or suspect surface, return one call:
The value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.
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
Agent Workflows
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…
Agent Workflows
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…
Agent Workflows
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …
Agent Workflows
Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…