Monday.com
Audits for the Monday workflows that silently break: dead automations whose toggles still show green, workload widgets blind to subitem effort, mirror columns that go blank under permissions, and board sprawl no native view surfaces. Each entry ships with the tool, a user guide, and the prompts to build a similar one yourself.
intake|support|request|sla|incident). One page, RED/AMBER/GREEN verdict, dead and stale tables grouped by tier, deactivated-users-still-owning-automations callout. Surfaces what Monday's native automation center hides: the toggle stays green long after the automation died. Bundled 22-automation / 6-board / 8-active-plus-3-deactivated-user Apex Defense fixture, engineered to land on RED.
Claude could write this. Two reasons to prefer the script.
Some workplaces — defense, medical devices, finance, anywhere with a strict IT policy — won't let Claude or any AI tool touch production data. These tools run on your machine, with no Claude or AI in the data path — your Monday.com workspace data flows direct from your machine to api.monday.com/v2 and back, no third-party SaaS in between, no telemetry, no tokens leaving your environment. And even where AI is allowed, repeat workflows shouldn't cost tokens — a deterministic script runs the same way every time, for free, forever. The prompt guide on each entry shows how the tool was built with Claude; the downloads are what you run after.