CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An exceptionally actionable, well-sequenced checklist with explicit validation checkpoints and hard-won project-specific gotchas. Its main weaknesses are the complete absence of progressive disclosure (everything inlined in one large file) and a few spots where content is repeated or over-explained.

Suggestions

Split deep-dive material into one-level-deep reference files (e.g., references/rls-policies.md for the session-GUC wrapping syntax, references/frontend.md for the editor component contracts) and keep SKILL.md as a tighter top-to-bottom checklist that links to them.

Deduplicate the system_prompts instructions: the SCHEMA_MAPPINGS['triggers'] edit appears in both section 8 and section 10.5 — state it once and cross-reference it.

Trim the RLS paragraph to the canonical wrapped forms and the cast-placement rule, moving the Postgres InitPlan/parse-behavior rationale into a reference file or dropping it.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious project specifics ("the one in generate.py is duplicated and utils.py wins", "KINDS: [&str; N]. Increment N") and assumes Claude's competence, explaining no generic concepts. Minor trimming is possible: the RLS InitPlan mechanics paragraph goes deeper than needed, and the SCHEMA_MAPPINGS['triggers'] instruction is repeated in both section 8 and section 10.5.

4 / 5

Actionability

Fully executable throughout: exact commands ("cargo sqlx migrate add -r add_{kind}_trigger", "./update_sqlx.sh", "python3 system_prompts/generate.py"), exact file paths, required struct/trait members, grep targets ("Grep for gcp_trigger / GcpTrigger"), and copy-paste router-mounting snippets cover the common cases.

5 / 5

Workflow Clarity

"Follow the checklist top-to-bottom" with 14 ordered sections, and this batch multi-file operation has explicit validation: section 11 gives concrete verification commands, section 14 is a PR checklist with migration revert/re-apply, and feedback loops like re-running cargo check to surface the array-length mismatch are spelled out.

5 / 5

Progressive Disclosure

Headers and numbered sections give good navigation, but the skill is a 289-line single file with no bundle files at all, so content that could live one level deep (RLS policy syntax, common pitfalls, per-surface frontend/CLI checklists) is inlined. This matches 'some structure but content that should be separate is inline' rather than the well-split structure of a 4.

3 / 5

Total

17

/

20

Passed

Description

75%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.

A strong description with a clear what, an explicit 'Use when' clause, and concrete provider trigger terms. It is specific and unlikely to fire for unrelated skills, falling just short of top marks on user-utterance-style triggers and full synonym coverage.

DimensionReasoningScore

Specificity

"adding a new TriggerCrud-based trigger type" and "wiring a new trigger kind across backend, frontend, CLI, and capture infrastructure" name several concrete surfaces, going beyond the 1-2 actions of a score-3 anchor. It stops short of 5 because it centers on a single verb (adding/wiring) rather than enumerating multiple distinct actions such as migration, OpenAPI, or sync wiring.

4 / 5

Completeness

It clearly states what it does ("Checklist for adding a new TriggerCrud-based trigger type to Windmill") and has an explicit "Use when wiring a new trigger kind..." clause. The when-clause is task-framed rather than phrased as concrete user utterances (e.g., "when the user asks to add an Azure or Kafka trigger"), so it does not reach the explicit trigger-phrase level of a 5.

4 / 5

Trigger Term Quality

"Azure, GCP, Kafka", "trigger", "Windmill", and "CLI" are natural terms a user would say when requesting this skill. A few natural terms are missing (e.g., "webhook", "event source", other providers like SQS/MQTT), which keeps it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"TriggerCrud-based trigger type to Windmill (Azure, GCP, Kafka)" carves out a clear niche with distinct provider triggers. There is minor overlap risk with the sibling native-trigger skill (Nextcloud, Google Drive) whose boundary is only disambiguated in the body, not in the description itself.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.