DEVOPS
Daily build-cache hit-rate scorecard across pipelines
Runs every morning to roll up the prior day's CI cache hit rates per project and job, writes a trend snapshot to Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionPull prior-day pipelines and job cache statsGitLab
- ActionWrite daily hit-rate snapshot to PostgresPostgres
- LogicRank largest declines vs trailing week
- OutputPost ranked cache scorecard to SlackSlack
What it does
Once a day it aggregates the previous 24 hours of CI pipeline cache stats, computes per-project and per-job hit rates, and compares them to the trailing week. It stores the daily snapshot in Postgres for trend history and posts a Slack scorecard ranking the caches that lost the most ground.
When to use it
Use it as a standing health report so cache degradation is visible before it becomes a fire. Unlike the real-time detectors, this is the slow-moving dashboard that surfaces gradual erosion, newly added jobs with no caching, and which teams' pipelines are quietly getting more expensive.
How it works
- 1A scheduled trigger fires each morning.
- 2The flow pulls the prior day's pipeline and job records from GitLab and parses cache restore/save outcomes.
- 3It computes per-job hit rates and writes the daily snapshot to Postgres.
- 4It reads the trailing-week history from Postgres and ranks the largest declines.
- 5It posts a ranked scorecard, with sparkline-style deltas, to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.