skills.rest
Jamkris
JamkrisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

automation-audit-ops

Audit ECC automation surfaces and report live states with evidence sources.

86|21|Updated Feb 9, 2026
Search Tags:#automation#audit#observability#reliability#inventory#workflows#ecc
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill automation-audit-ops-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automation-audit-ops
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/automation-audit-ops
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill automation-audit-ops-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ECC automation surfaces (local runtime hooks, repo CI, MCP configs, connectors, wrappers) are often live, broken, redundant, or missing, and it is hard to know where to start before acting. This skill provides an evidence-first inventory and an audit workflow to surface the current state and guide fixes.

Core Features & Use Cases

  • Inventory live surfaces across the stack (local runtime, repo CI, MCP servers, connectors, wrappers)
  • Classify each item by live state: configured, authenticated, recently verified, stale or broken, missing
  • Trace the evidence path with concrete sources: file paths, workflow runs, hook logs, config entries
  • End with a single, actionable recommendation: keep, merge, cut, or fix-next

Quick Start

Audit your ECC surface to generate an evidence-backed inventory and a keep/merge/cut/fix-next plan before rewriting anything.

Frequently Asked Questions about automation-audit-ops

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

FAQPage Schema
How do I inventory all my automation surfaces across local hooks, CI, and MCP servers?▼

To inventory automation surfaces, you audit local runtime hooks, repo CI workflows, MCP configs, connectors, and wrappers to classify their live state as configured, authenticated, stale, broken, or missing.

What is the best way to audit broken or stale GitHub Actions and cron jobs?▼

The best way to audit broken or stale GitHub Actions and cron jobs is to trace concrete evidence paths like workflow runs and hook logs, then classify each item by its live authentication and verification state.

How do I generate a keep, merge, cut, or fix-next plan for redundant repo automations?▼

You generate a keep, merge, cut, or fix-next plan by auditing all configured automations, capturing evidence sources like file paths and logs, and mapping each item to a structured actionable recommendation.

Does this automation audit require any external dependencies or connectors?▼

No, this automation audit requires no external dependencies, relying solely on its internal workflow to inspect local runtime environments, repo CI, MCP servers, and app integrations directly.

Why are my MCP server connectors and wrappers showing as missing or broken?▼

MCP server connectors and wrappers show as missing or broken when the audit traces their evidence paths through config entries and logs, failing to find recent verification or active authentication states.

Related Skills

Explore More Software Engineering Skills→
llmh333llmh333

automation-audit-ops

Audit live automation surfaces and classify jobs, hooks, connectors, MCP servers, or wrappers.

Community
Advanced
luongldptitluongldptit

automation-audit-ops

Inventory live, broken, redundant, and missing ECC automation surfaces with proof-backed classification.

Community
Advanced
dezverevdezverev

sync-dev-guide

Synchronize GeneralDevGuide with skills, agents, and MCP server inventory.

Community
Basic
binan-makerbinan-maker

security_scan

Aggregate security scanner results into a prioritized summary with per-scanner status.

Community
Advanced