Audit My Automations
Skill8 starsChanged 5 months agoMITView on GitHub
Health-check every automation in the workspace — which are firing, which have gone stale, which are erroring, which are missing safety dials (dedup, daily caps), and which overlap with each other. Surfaces problems in priority order with a one-line fix for each.
In this repository101 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- Add a FieldSkill
- Assemble Content PackSkill
- Assemble PackSkill
- Audit My DataSkill
- automate-thisSkill
- Brand My WorkspaceSkill
- Break Down A ChannelSkill
- Build Brand StrategySkill
- Build Customer VoiceSkill
- Build DocumentSkill
- Build FormSkill
- Build Knowledge Base From DocsSkill
- Build My ProofSkill
- Build My VoiceSkill
- Build Social StrategySkill
- Build SpreadsheetSkill
- Build Work Order ProcessSkill
- Cash Flow ForecastSkill
- Coach My CallsSkill
- Compare DocumentsSkill
- Connect A ToolSkill
- Delegate This WorkSkill
- Describe A ProductSkill
- Design My ScenesSkill
- Design Nurture SequenceSkill
- draft-replySkill
- Email Me A ReportSkill
- Estimate My BASSkill
- Extract DocumentSkill
- Find My Next MoveSkill
- Five Day ChallengeSkill
- Follow-up RadarSkill
- Form RadarSkill
- Get Found OnlineSkill
- Grill Me On This DecisionSkill
- import-from-anywhereSkill
- lead-triageSkill
- Learn My BusinessSkill
- Lint DocumentSkill
- Lint FormSkill
- Lint Nurture SequenceSkill
- log-this-callSkill
- make-it-happenSkill
- Make My VideoSkill
- Make Product DemoSkill
- Make Social PostSkill
- Make ThumbnailSkill
- missed-call-recoverySkill
- Nurture HealthSkill
- Onboard Team MemberSkill
- Outstanding DocumentsSkill
- Outstanding InvoicesSkill
- Package My VideoSkill
- Plan My AdsSkill
- Plan My ContentSkill
- Plan My RoadmapSkill
- Plan My YouTubeSkill
- Prep For CallSkill
- Price My WorkSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
If the script can't run (auth/network), fall back to mcp__trustpager__list_automations + mcp__trustpager__list_automation_runs per …
- Very specific: line 84
Never delete an automation without explicit confirmation naming it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audit My Automations
Operators set automations up and never look at them again — so they don't notice when one silently stops firing, starts erroring, or sends twice. This skill is the regular check-up.
Read first: knowledge/automation-method.md — especially §6 (safety dials) and §8 (reading the run log). The flags this skill raises map directly to those sections.
Step 1 — Fetch the health digest
python ~/.claude/bos-run.py audit-my-automationsOne call: lists every automation (with triggers + actions inline), samples each one's recent runs, and computes per-automation flags plus cross-automation trigger overlaps. The shape is documented at the bottom of fetch.py.
If the script can't run (auth/network), fall back to mcp__trustpager__list_automations + mcp__trustpager__list_automation_runs per automation — but that's many calls; prefer the script.
Step 2 — Present the report, worst first
Lead with what's broken, then what's risky, then a one-line "healthy" tally. Never dump all automations as a flat list.
🔧 NEEDS ATTENTION (N)
→ "Renewal reminder" — 3 failed runs this week. Last error: <error_message>. → check it
→ "Old intake" — has a trigger but no actions (does nothing). → add actions or delete
⚠️ WORTH A LOOK (N)
→ "Quote follow-up" — enabled but hasn't fired in 41 days. Trigger may be wrong, or just quiet.
→ "Welcome email" — sends email but dedup is OFF — a double-submit double-emails. → turn dedup on
→ "Lead → quoting API" — calls a webhook with no daily cap. → set max_executions_per_day as a seatbelt
→ "Win celebration" — 9 of last 10 runs SKIPPED. Conditions may be too tight to ever pass.
🔁 OVERLAPS (N)
→ "Tag new lead" and "Email new lead" both fire on form_completed (Intake form).
Fine if intentional; consolidate into one automation with multiple actions if not.
✅ HEALTHY: 12 automations firing normally.What each flag means + the fix
| Flag | Meaning | Fix to offer |
recent_failures_N | actions errored on recent runs | open it, read error_message; /why-didnt-it-fire for the detail |
no_actions | trigger fires but nothing happens | add actions, or delete the automation |
no_triggers | nothing can fire it (and not a stage automation) | add a trigger, or it's dead weight |
never_run | enabled but never fired | trigger/source likely wrong, or genuinely no events yet |
stale_Nd | enabled, no run in N days (≥30) | confirm the trigger still matches reality; not always a problem |
mostly_skipped | ≥80% of recent runs skipped | conditions too tight — they rarely pass |
sends_without_dedup | a send action, dedup OFF | turn dedup on so a double-event doesn't double-send |
webhook_without_daily_cap | call_webhook/feedback action, no daily cap | set max_executions_per_day as a runaway-loop seatbelt |
disabled | switched off | informational — list under a "staged/off" count, not as a problem |
Step 3 — Offer fixes (with approval)
For the safe, mechanical fixes, offer to apply them — one at a time, with a yes:
- Turn on dedup →
mcp__trustpager__update_automation(automation_id, dedup_enabled=true, dedup_window_minutes=60) - Set a daily cap →
update_automation(automation_id, max_executions_per_day=N) - Disable a redundant duplicate →
mcp__trustpager__disable_automation(automation_id)
Never delete an automation without explicit confirmation naming it. For "why is it failing / skipping" deep-dives, hand to /why-didnt-it-fire. For building a missing automation, /automate-this.
What to never do
- ❌ Don't present automations alphabetically or as one flat list — rank by severity.
- ❌ Don't auto-apply fixes. Offer, get a yes, then apply — one at a time.
- ❌ Don't flag
disabledas broken — staged/off is a valid state. Count it, don't alarm about it. - ❌ Don't treat
skippedruns as failures — that's conditions working as designed. Onlymostly_skippedis worth a mention.
Output shape
Open with the headline tally ("18 automations: 12 healthy, 2 need attention, 4 worth a look"), then the prioritised sections, then the single most important fix to make first.
Does 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.

