Audit scheduled jobs, hooks, MCP servers, and external integrations using configuration files, logs, and recent runs. Distinguish configured tools from verified working ones, identify failures or overlap, and recommend what to keep, merge, remove, or fix next.
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.
Review the instructions the agent will receive before you install.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.
Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.
Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.