automation-audit-ops
Skill0 starsChanged 2 months agoMITView on GitHub
Evidence-first inventory of live automations — cron, GitHub Actions, hooks, MCP servers, wrappers, and connectors — then keep / merge / cut / fix-next. Use when asking what is live, broken, redundant, or missing before changing anything. Not for skill-catalog hygiene (skill-stocktake), agent-loop diagnosis (agent-architecture-audit), or GitHub issue/PR operations (gh-axi).
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- gongyijie85/dsh-ecctheir own version, first seen Oct 13, 2026
- Fmarzochi/EGCtheir own version, first seen Sep 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- Fmarzochi/EGC★ 61same name
- pekral/cursor-rules★ 10same name
- gongyijie85/dsh-ecc★ 8same name
- Rojios/everything-claude-code★ 1same name
- SamuelNDCE/claude-super-skill-library★ 1same name
- davidanthonyn/claude-skills★ 0same name
- pankaj-mahaur/Agent-Daemon★ 0same name
- renepf/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- found-this-designSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-craftSkill
- scroll-worldSkill
- skill-stocktakeSkill
- smartbook-ingestSkill
- smartdocSkill
- supabase-opsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vercel-opsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 1 is common, 1 is distinctive, and 0 are very specific to this project.
1
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read-only operator audit of automations.
- Common: line 22
Start read-only unless the user explicitly asked for fixes.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Automation Audit Ops
Read-only operator audit of automations. Produce an evidence table before rewriting anything.
Boundaries & Handoffs
| Need | Route |
| Skill catalog frontmatter and boundary hygiene | skill-stocktake |
| Agent wrapper, tool-loop, or context leakage diagnosis | agent-architecture-audit |
| Filing or merging GitHub issues, PRs, workflow runs | gh-axi |
| Secrets, auth, or privileged webhook review | full-audit-keamanan |
| Live cron / CI / hook / MCP / wrapper inventory | automation-audit-ops |
Start read-only unless the user explicitly asked for fixes.
Procedure
Consult references/inventory.md for live-state labels.
- Inventory the surface. Repo hooks, GitHub Actions and schedules, MCP configs, wrapper scripts, connector entries. Group: local runtime, CI, external systems, notifications.
- Classify live state. Configured, authenticated, recently verified, stale/broken, missing. Presence in config is not proof of working.
- Cite a proof path for every important claim: file, workflow run, hook log, command output, or failure signature. Ambiguity stays labeled ambiguous.
- Recommend keep / merge / cut / fix-next per overlapping or suspect item. Name one canonical lane. Do not delete until the table exists.
Output
CURRENT SURFACE
- automation / source / live state / proof
FINDINGS
- breakage / overlap / stale / missing
RECOMMENDATION
- keep / merge / cut / fix-nextDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.