AI AGENTS
License-risk triage to Linear
On a webhook from your model registry, an agent checks a HuggingFace model card's license against your allowlist and, when the license is restrictive or ambiguous, opens a Linear…
How it runs
The automated pipeline, trigger to output.
- TriggerRegistry webhook with model idHTTP webhook
- ActionFetch model card and licenseHugging Face
- LogicClassify license vs allowlist
- LogicStop if license is clear
- OutputOpen Linear issue for reviewLinear
What it does
Catches license risk the moment a model enters your registry. The agent reads the HuggingFace model card's license, compares it to your approved list, and only escalates the cases that actually need a human — creating a tracked Linear issue with the specifics.
When to use it
Use when license compliance is a hard requirement and you can't ship a model under a non-commercial, gated, or undeclared license without sign-off. Routes ambiguous cases to legal instead of letting them slip through.
How it works
- 1Your registry fires a webhook with the model id when a model is added.
- 2The agent fetches that model's card and license metadata from HuggingFace.
- 3A logic step compares the license to your allowlist and classifies it as clear, restrictive, or undeclared.
- 4Clear, allowlisted licenses end the run with no action.
- 5For restrictive or undeclared licenses, the flow opens a Linear issue with the model, its license, and the reason for review.
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
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.