CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triggers

MUST use when configuring triggers.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/triggers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 body is a dense, high-signal reference: exact naming patterns, payload shapes, executable SDK snippets, and safety-gated CLI commands with no filler. Its two real gaps are the missing example of an actual trigger YAML (the core artifact a user configures) and the absence of any validation step around the destructive `wmill sync push` operation.

Suggestions

Add one minimal example of a complete trigger configuration YAML (e.g. `f/inbound/orders.email_trigger.yaml` with its runnable path, `workspaced_local_part`, and a preprocessor) so the common creation task is fully executable.

Add a validation/checkpoint step around the destructive `wmill sync push` — e.g. run `wmill sync pull --dry-run` (or a push dry-run if available) and show the user the diff, then push only on explicit confirmation.

Consider moving the email payload/S3 attachment detail (headers, `email_extra_args`, S3 fallback string, parquet feature note) into a `references/email-triggers.md` and keeping a brief summary in SKILL.md, since the email section dominates the file.

DimensionReasoningScore

Conciseness

Every line carries non-obvious, Windmill-specific facts — the file-naming pattern, the workspaced_local_part behavior, the 1 MiB raw_email S3 cutoff, the S3 fallback string, the parquet build-feature requirement — with no padding or explanation of concepts Claude already knows. The one-sentence intro ('Triggers allow external events to invoke your scripts and flows.') is the only general statement and is minimal. This matches 'Lean and efficient; assumes Claude's competence; every token earns its place'; nothing to trim, so not a 4.

5 / 5

Actionability

Guidance is largely executable: exact file-naming pattern with four concrete examples, exact payload shapes, copy-paste TypeScript/Python for loading S3 attachments, and concrete CLI commands (`wmill sync push/pull`, `sync pull --dry-run`). It falls short of 5 because the most common case — what a trigger configuration YAML actually contains (fields like the runnable path, `workspaced_local_part`, preprocessor setup) — is never shown, only the file naming; it is above 3 because all shown code is executable, not pseudocode.

4 / 5

Workflow Clarity

The skill itself flags that deploying is destructive ('Deploying local changes to the workspace can be destructive to remote state') and correctly gates it on explicit user intent, and offers `sync pull --dry-run` as a preview checkpoint. However, the destructive `wmill sync push` path has no validation or verification step (no dry-run, no post-push check), and the judging guidelines explicitly cap workflow clarity at 3 for destructive operations lacking validation. It is not a 2 because the sequence and destructive-ness warnings are explicit, and not a 4 because the push path has no checkpoint at all.

3 / 5

Progressive Disclosure

The body is well-organized into scannable sections (File Naming, Email Triggers, Payload, Attachments, CLI Commands) and is appropriately self-contained for its size, with no nested or buried references — its only pointer ('see the Deploying section in AGENTS.wmill.md') is one level deep and clearly signaled. It is not a 5 because the content exceeds the under-50-line simple-skill threshold (~66 lines) and the email-trigger payload detail (headers, extras, S3 semantics) is the kind of deeper material that would fit a reference file; it is above 3 because nothing is misplaced and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

36%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 minimal to a fault: it provides a usable trigger clause ('when configuring triggers') but completely omits what the skill does and offers no natural synonyms or Windmill/wmill keywords that would help discovery or disambiguation. It reads more like a routing directive than a description.

Suggestions

State what the skill does in third person, e.g. "Creates and deploys Windmill trigger configuration files ({path}.{type}_trigger.yaml) for webhook, Kafka, Postgres CDC, and email triggers."

Add natural trigger terms users would say — webhook, email trigger, cron/schedule, event, wmill sync — and a Windmill/wmill qualifier to distinguish it from CI/CD or database trigger skills.

Expand the 'when' clause to concrete moments, e.g. "Use when the user asks to set up, modify, or deploy a Windmill trigger, or route emails to a script/flow."

DimensionReasoningScore

Specificity

The description "MUST use when configuring triggers." names the domain (triggers) but states zero concrete actions — it never says what the skill does (create, deploy, or manage trigger configurations). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no concrete action is listed at all, and not a 1 because the domain is named rather than being pure abstraction.

2 / 5

Completeness

The description has an explicit 'when' clause ("when configuring triggers") but no 'what' — the skill's purpose (creating/managing Windmill trigger configuration files, handling email/webhook triggers) is entirely unstated. Per the anchor 'only when is present without what', this is a 2; not a 1 because the when clause is clear and domain-anchored, and the cap noted in the guidelines (missing 'Use when...' capped at 3) is not triggered since 'when' is present — but the missing 'what' pulls it to 2.

2 / 5

Trigger Term Quality

"triggers" is the natural term a user would say for this domain, but coverage stops at that single keyword — no variations or synonyms a user might actually utter (webhook, email trigger, schedule, cron, event, push/deploy, wmill). This fits 'Some relevant keywords but missing common variations or synonyms'; it is above a 2 because the keyword is domain-specific rather than generic ('works with files'), but below a 4 because nearly all natural phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

"configuring triggers" carves out a real niche but the word 'triggers' is used by many ecosystems (CI/CD pipelines, GitHub Actions, database triggers, event systems), so it could fire for the wrong skill outside a Windmill context. This fits 'Somewhat specific but could still overlap with similar skills'; not a 4 because no Windmill-specific qualifier (e.g., 'Windmill', 'wmill') disambiguates it.

3 / 5

Total

10

/

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

system_prompts/auto-generated/skills/triggers/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.