AI AGENTS
Model Card Update Webhook -> Linear Eval Task
Receives a HuggingFace model-card update webhook, classifies whether the change is substantive (new weights, new benchmark, license shift), and files a triaged Linear issue…
How it runs
The automated pipeline, trigger to output.
- TriggerHuggingFace card-update webhook arrivesHTTP webhook
- ActionFetch current and prior model cardHugging Face
- LogicClassify edit: cosmetic vs substantive
- ActionDraft change summary + eval checklist
- OutputCreate assigned Linear eval issueLinear
What it does
Turns noisy model-card edits into a clean, human-owned decision queue. When a watched model's card changes, the workflow figures out whether the edit actually matters and, if so, creates a Linear issue pre-filled with what changed and the eval steps required before any production swap.
When to use it
Use it when you want a human in the loop rather than an automatic PR, but you don't want to manually monitor HuggingFace. Good for regulated teams where every model change needs a tracked ticket and an owner.
How it works
- 1A HuggingFace card-update webhook delivers the changed model id and diff payload.
- 2The agent fetches the current and prior card to compute what actually changed.
- 3A branch classifies the edit: cosmetic (stop) versus substantive — new weights, revised benchmark, or license change.
- 4For substantive changes it drafts a summary plus the fixed-eval checklist and a recommended priority.
- 5It creates a Linear issue in the model-ops project, assigns the rotation owner, and tags the affected service.
- 6The issue body links back to the model card revision so the engineer can reproduce the eval.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.