automation-audit-ops

Audits GitHub Actions, local hooks, and MCP configurations for operational status and redundancy.

1|Updated Apr 6, 2026

Search Tags:#automation #workflow #audit #maintenance #github-actions #inventory

Ready to run

npx skills add https://github.com/vrcms/everything-qwen-code --skill automation-audit-ops-vrcms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automation-audit-ops
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/automation-audit-ops
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill automation-audit-ops-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity regarding the state of your automation infrastructure by providing a clear, evidence-backed inventory of what is currently live, broken, or redundant.

Core Features & Use Cases

Surface Inventory: Automatically catalogs GitHub Actions, local hooks, MCP servers, and connector integrations.
State Classification: Categorizes every automation as configured, authenticated, verified, stale, or broken.
Strategic Recommendations: Provides a clear keep, merge, cut, or fix-next path to consolidate your automation into a single canonical lane.

Quick Start

Ask the agent to perform an audit of all current automations to identify broken workflows and redundant configurations.

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 my GitHub Actions workflows and local hooks for redundancy?▼

To audit GitHub Actions workflows and local hooks, you need an evidence-based inventory that categorizes every automation as configured, authenticated, verified, stale, or broken. This process reconciles live repository state with configured tooling to identify redundant configurations.

What is the best way to inventory and classify the state of MCP servers and connectors?▼

The best way to inventory MCP servers and connectors is to perform a read-only audit of configuration manifests and repository hooks. This classifies operational status by checking if integrations are currently live, broken, or redundant.

Does auditing automation infrastructure require write access to my repository?▼

No, auditing automation infrastructure requires only read-only access to repository hooks, workflow files, and configuration manifests. This ensures the audit can safely inventory operational status without modifying your live repository state.

How do I consolidate broken workflows into a single canonical automation lane?▼

You can consolidate broken workflows by generating strategic recommendations that provide a clear keep, merge, cut, or fix-next path. This uses the audit evidence to merge redundant configurations and eliminate stale automations.

When should I perform a maintenance audit on my automation stack?▼

You should perform a maintenance audit on your automation stack when you need to reconcile live repository state with configured tooling. This is essential for cleanup tasks where ambiguity exists regarding what is currently live, broken, or redundant.