automation-audit-ops

Audit live automations, hooks, and connectors to produce evidence-backed keep, merge, cut, or fix recommendations.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill automation-audit-ops-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automation-audit-ops
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/automation-audit-ops
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill automation-audit-ops-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Workspaces accumulate cron jobs, GitHub Actions, local hooks, MCP servers, connectors, and wrapper scripts over time, and it becomes unclear which ones are live, broken, redundant, or missing. This Skill produces an evidence-first inventory and overlap audit before any fixing or rewriting begins. ## Core Features & Use Cases - Live Surface Inventory: Reads repo hooks, GitHub Actions, scheduled workflows, MCP configs, connectors, and wrapper scripts, grouped by surface such as local runtime, CI, external systems, and notifications. - State Classification: Labels every automation as configured, authenticated, recently verified, stale or broken, or missing, then classifies the problem type such as active breakage, auth outage, or redundancy. - Evidence-Backed Recommendations: Every claim cites a concrete proof path (file, workflow run, hook log, config entry), ending in a keep / merge / cut / fix-next decision per surface. - Use Case: When a user asks "what automations do I actually have running and which are broken?", this Skill audits the real workspace state and returns one canonical lane instead of preserving every historical path. ## Quick Start Ask the assistant to audit which automations, hooks, and connectors in this workspace are live, broken, or overlapping, and to recommend what to keep, merge, cut, or fix next.

Frequently Asked Questions about automation-audit-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit which automations are running in my workspace?▼

Inventory the real surface first: read repo hooks, GitHub Actions, scheduled workflows, MCP configs, connectors, and wrapper scripts. Then classify each item as configured, authenticated, recently verified, stale or broken, or missing, backing every claim with a file path, workflow run, or log entry.

How to find redundant or overlapping automation jobs and hooks?▼

Group all surfaced automations by surface such as local runtime, CI, external systems, and notifications, then flag items doing the same work. Only after the evidence table exists should you assign a keep, merge, cut, or fix-next call to collapse duplicates into one canonical lane.

Does a configured GitHub Action or MCP server mean it is working?▼

No. Presence in config only proves something is configured, not authenticated or recently verified. The audit separates configured, authenticated, and recently verified states, and requires a concrete proof path like a recent workflow run or hook log before calling anything live.

When should I fix automation overlap versus broken jobs first?▼

Name the broken high-signal path before fixing lower-value redundancy. The workflow classifies problem types such as active breakage, auth outage, stale status, and overlap, so active breakage gets prioritized over merging duplicate surfaces.

What are the limitations of an audit-first automation review?▼

The audit starts read-only and does not rewrite anything unless the user explicitly asks for fixes. If the current state of an automation is ambiguous, the audit reports that ambiguity directly rather than claiming completeness.