adding-a-trigger

Checklist for adding a new TriggerCrud-based trigger type to Windmill (Azure, GCP, Kafka, etc.). Use when wiring a new trigger kind across backend, frontend, CLI, and capture infrastructure.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exceptionally actionable, well-sequenced checklist that assumes competence and supplies exact paths, code, and commands with explicit validation checkpoints. Its only weakness is that all detail lives inline in SKILL.md with no reference files to offload the longer gotchas.

Suggestions

Move the RLS session-GUC explanation (§1) and the §12 Common pitfalls list into a references/ file (e.g. references/pitfalls.md) and link to them, shrinking SKILL.md to a tighter overview.

Consider extracting the per-file frontend/CLI bullet lists (§9–§10) into a references/wiring-detail.md to improve progressive disclosure now that the doc exceeds 50 lines.

Add a short "Reference implementations" pointer at the top that links to a reference doc with grep examples, keeping the main body focused on the checklist sequence.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence across Rust/Svelte/SQL/axum with no concept padding; even the RLS sub-select explanation is justified non-obvious project knowledge, so every token earns its place.	5 / 5
Actionability	Provides exact file paths, struct/trait names, copy-paste code blocks, and specific commands ("cargo sqlx migrate add -r", "./update_sqlx.sh", "npm run generate-backend-client") that are directly executable.	5 / 5
Workflow Clarity	Sequenced numbered sections 1–14 top-to-bottom with an explicit Validation section (§11) and a final checkbox checklist (§14); validation is present so no destructive/batch cap applies, and pitfalls supply fix-and-retry feedback loops.	5 / 5
Progressive Disclosure	No bundle files exist and the document is a single 283-line checklist, but it is well organized with clear numbered section headers and easy navigation; some inlined detail (RLS gotcha, pitfalls) could be split into references, which keeps it just short of a 5.	4 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states a concrete purpose, names the target domain and surfaces, and provides an explicit "Use when" trigger clause. It is distinguishable from sibling skills and carries low conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain (adding a TriggerCrud-based trigger type to Windmill) and several concrete surfaces — "backend, frontend, CLI, and capture infrastructure" — with named examples (Azure, GCP, Kafka), though it does not enumerate individual discrete actions comprehensively enough for a 5.	4 / 5
Completeness	Explicitly answers both what ("Checklist for adding a new TriggerCrud-based trigger type to Windmill") and when ("Use when wiring a new trigger kind across backend, frontend, CLI, and capture infrastructure") with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes natural phrases a developer would say ("adding a new trigger type", "wiring a new trigger kind") plus named kind synonyms (Azure, GCP, Kafka), but is missing some common variations a user might naturally voice.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (TriggerCrud-based Windmill triggers with named kinds) that is unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: windmill-labs/windmill
Path: .agents/skills/adding-a-trigger/SKILL.md
Commit: 2fb7903

Reviewed: ~13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.