Heroku To AWS
aws/agent-toolkit-for-aws
Migrate workloads from Heroku to AWS. An agent skill from aws/agent-toolkit-for-aws.
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
Install Windmill Trigger Type Checklist
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install windmill-labs/windmill adding-a-trigger --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-a-trigger .claude/skills/adding-a-trigger && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .claude/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-triggerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install windmill-labs/windmill adding-a-trigger --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-a-trigger .agents/skills/adding-a-trigger && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .agents/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install windmill-labs/windmill adding-a-trigger --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-a-trigger .cursor/skills/adding-a-trigger && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .cursor/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/windmill-labs/windmill.git --path .agents/skills/adding-a-trigger--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install windmill-labs/windmill adding-a-trigger --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-a-trigger .gemini/skills/adding-a-trigger && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .gemini/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install windmill-labs/windmill adding-a-triggerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-a-trigger .github/skills/adding-a-trigger && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .github/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add windmill-labs/windmill --skill adding-a-trigger -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install windmill-labs/windmill adding-a-trigger --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/windmill-labs/windmill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-a-trigger .opencode/skills/adding-a-trigger && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adding-a-trigger" agent skill from https://github.com/windmill-labs/windmill/tree/main/.agents/skills/adding-a-trigger into .opencode/skills/adding-a-trigger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-a-trigger", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
adding-a-trigger- GitHub stars
- 18k
- Token cost
- ~4.7k tokens
- SKILL.md length
- 1,843 words
- Files
- 1
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
- Works in 12 steps: Database migration → Backend crate (windmill-trigger-{kind}) → Wire into windmill-api (feature-gated… → …
- Adding a new TriggerCrud-based trigger kind to Windmill
- SKILL.md covers Reference implementations, 1. Database migration, 2. Backend crate… and 3. Wire into windmill-api…, plus 13 more sections
- Calls cargo, npm and python3
What it does
The skill lists each file that has to change when a new trigger kind is added to Windmill, because missing one causes silent regressions: sync drops the trigger, the capture button does nothing, workspace forks lose it or sidebar counters undercount. It is for kinds that implement TriggerCrud, such as Kafka, GCP, Azure, MQTT, SQS, NATS, Postgres or Email. Native triggers wired through windmill-native-triggers use a different skill.
It names GCP, Kafka and Azure as reference implementations and works from the top down, starting with a database migration created by cargo sqlx migrate add -r from the backend folder, never with hand-typed timestamps. The migration defines a trigger table that mirrors the Kafka and GCP tables, indexes, a foreign key to workspace and the row-level security policies copied from an existing trigger table, with session settings wrapped in scalar sub-selects. The kind name is written in lower, Pascal and upper case throughout.
When your agent uses it
- Adding a new TriggerCrud-based trigger kind to Windmill
- Auditing a trigger pull request for files missed across backend, frontend and CLI
- Wiring capture support for a new trigger type
Example prompts
- “Add an MQTT trigger type to Windmill, following the Kafka implementation.”
- “Check my Azure trigger branch against the new-trigger checklist and list what is missing.”
- “Write the sqlx migration for a new NATS trigger table.”
Requirements
- A Windmill source checkout
- cargo with sqlx for creating migrations
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- Database migration
- Backend crate (windmill-trigger-{kind})
- Wire into windmill-api (feature-gated everywhere)
- TriggerKind enum (backend/windmill-types/src/triggers.rs)
- OpenAPI (backend/windmill-api/openapi.yaml)
- UsedTriggers + workspace export
- Capture infrastructure (backend/windmill-api/src/capture.rs)
- CLI (cli/) — easy to miss, breaks sync silently
- Frontend — editor + drawer
- Frontend — global integration
- Validation
- Common pitfalls
What it can do on your machine
Read from SKILL.md and the folder at commit eab3dd5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargonpmpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Windmill Trigger Type Checklist loads about 4.7k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 1,843 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,843 words (~4,694 tokens).
“Use this skill when adding a trigger kind that implements TriggerCrud (Kafka, GCP, Azure, MQTT, SQS, NATS, Postgres, Email…). For native triggers (Nextcloud, Google Drive — things wired through windmill-native-triggers), use the native-trigger skill instead.”
- name
- adding-a-trigger
Files
Just SKILL.md in .agents/skills/adding-a-trigger of windmill-labs/windmill.
Open the folder on GitHubat commit eab3dd5
Compare with similar skills
Windmill Trigger Type Checklist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Windmill Trigger Type Checklist this skillwindmill-labs/windmill | 18k | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| Heroku To AWSaws/agent-toolkit-for-aws | 2.8k | — | ~7.2k | Automated safety check: Pass | Apache-2.0 | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Create Environmentgodatadriven/whirl | 205 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Event Store Designwshobson/agents | 40k | 8 repos | ~828 | Automated safety check: Pass | MIT | |
| Ak Cloud Deployyaalalabs/agent-kernel | 191 | — | ~14k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
Create Environment
godatadriven/whirl
Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.
Event Store Design
wshobson/agents
Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.
Ak Cloud Deploy
yaalalabs/agent-kernel
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart.
- Official
Azure Event Hubs
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Event Hubs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations &…
More from windmill-labs/windmill
All 42 skills in this repoWindmill AI Evals
windmill-labs/windmill
Writes and runs black-box benchmark cases for Windmill's flow, app, script, CLI and global AI generation modes, including before-and-after comparisons.
Domain Modeling and Glossary
windmill-labs/windmill
Actively challenges vague or conflicting terminology as you design, and keeps a living domain glossary file up to date in real time.
Local PR Review
windmill-labs/windmill
Runs the same code review locally that GitHub's auto-review actions run on a PR, delegating to a fresh-context subagent so the review isn't biased by the main session's own reasoning.
Draft PR with CI Rounds
windmill-labs/windmill
Opens a draft GitHub pull request with a conventional title and explicit body, then drives CI review rounds before marking it ready.
Windmill Dev Page Preview
windmill-labs/windmill
Opens the Windmill dev page to preview a flow, script or app, choosing between proxy and direct mode and deciding whether the agent or the runtime starts the wmill dev server.
Windmill Rust Backend Patterns
windmill-labs/windmill
Sets Rust conventions for the Windmill backend: error types, SQLx queries, JSON handling, async rules, module layout and rust-analyzer navigation.
Related
Categories
Questions about Windmill Trigger Type Checklist
What does Windmill Trigger Type Checklist do?
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill. The skill lists each file that has to change when a new trigger kind is added to Windmill, because missing one causes silent regressions: sync drops the trigger, the capture button does nothing, workspace forks lose it or sidebar counters undercount. It is for kinds that implement TriggerCrud, such as Kafka, GCP, Azure, MQTT, SQS, NATS, Postgres or Email.
When should I use Windmill Trigger Type Checklist?
Windmill Trigger Type Checklist fits situations like: adding a new TriggerCrud-based trigger kind to Windmill; auditing a trigger pull request for files missed across backend, frontend and CLI; wiring capture support for a new trigger type.
How do I install Windmill Trigger Type Checklist in Claude Code?
Run `npx skills add windmill-labs/windmill --skill adding-a-trigger -a claude-code`. Or copy the skill folder (.agents/skills/adding-a-trigger in windmill-labs/windmill) into .claude/skills/adding-a-trigger in your project. Claude Code loads it when a task matches its description.
How do I install Windmill Trigger Type Checklist in Codex?
Run `npx skills add windmill-labs/windmill --skill adding-a-trigger -a codex`. Or copy the skill folder (.agents/skills/adding-a-trigger in windmill-labs/windmill) into .agents/skills/adding-a-trigger in your project. Codex loads it when a task matches its description.
Can I use Windmill Trigger Type Checklist in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add windmill-labs/windmill --skill adding-a-trigger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-a-trigger, .gemini/skills/adding-a-trigger, .github/skills/adding-a-trigger and .opencode/skills/adding-a-trigger in your project.
What does Windmill Trigger Type Checklist need to run?
Going by SKILL.md and its folder, Windmill Trigger Type Checklist needs the command-line tools its instructions call (cargo, npm and python3). Our summary lists: A Windmill source checkout; cargo with sqlx for creating migrations.
Does Windmill Trigger Type Checklist access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Windmill Trigger Type Checklist safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Windmill Trigger Type Checklist use?
Windmill Trigger Type Checklist has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Windmill Trigger Type Checklist use?
About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Windmill Trigger Type Checklist?
Skills that share tags, products or a category with Windmill Trigger Type Checklist: Heroku To AWS (aws/agent-toolkit-for-aws, 2.8k stars), Foundatio (FoundatioFx/Foundatio, 2.1k stars), Create Environment (godatadriven/whirl, 205 stars) and Event Store Design (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Windmill Trigger Type Checklist?
windmill-labs (a GitHub organization) maintains it in windmill-labs/windmill, which has 18,117 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 7, 2026.
Source: windmill-labs/windmill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.