Get a demo — 30 minutes →
Skill scan report

adding-a-trigger

View on GitHub
0 Clean No risk patterns detected.

What this skill does

A checklist and guide for adding new trigger types to a Windmill system (e.g., Azure, GCP, Kafka). It outlines the necessary changes across backend, frontend, CLI, and capture infrastructure.

github/windmill-labs - general - 17.5k stars

ThreatsNo threats detected

Threat analysis

No risk categories triggeredclean

Skill info

Namewindmill-labs/adding-a-trigger
Registrygithub
Version13b5216
PURLpkg:github/windmill-labs/windmill@13b5216?skill=adding-a-trigger
Stars17.5k

Assessments

No risk patterns detected in this scan. A clean automated scan is a good signal, not a guarantee.

Badge

Add the Anomity scan badge for adding-a-trigger to your README.

Anomity Skill Check badge

Markdown
[![Anomity Skill Check](https://anomity.ai/skills/badge.svg)](https://anomity.ai/skills/github/windmill-labs/adding-a-trigger/)
HTML
<a href="https://anomity.ai/skills/github/windmill-labs/adding-a-trigger/"><img src="https://anomity.ai/skills/badge.svg" alt="Anomity Skill Check"></a>
Image URL
https://anomity.ai/skills/badge.svg

How Anomity governs this at runtime

Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.

Book a 30-minute demo to see your own skill inventory.

Methodology and disputes

Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of adding-a-trigger? Report an issue or request a rescan.

Ask AI about Anomity
ChatGPT Claude Perplexity Google AI Grok