CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

native-trigger

Guidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/native-trigger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 implementation guide with copy-paste code, exact paths, and verification commands — clearly written by someone who knows the codebase. Its costs are token weight: duplicated pattern explanations and ~800 lines of inlined reference material that a bundle structure (trait reference, OAuth details, frontend checklist as separate files) would offload.

Suggestions

Split the skill into bundle files: keep SKILL.md as the architecture overview and step index, and move the full External trait reference, the Step 3 code template, and the OAuth/connections internals into references/ (e.g. TRAIT.md, TEMPLATE.md, OAUTH.md), linking each from the relevant step.

Remove the duplication between 'Create Lifecycle: Two Paths' and 'Skipping update+get After Create (Google Pattern)' — state the two-path choice once and cross-reference it from the trait template comments.

Embed per-phase validation checkpoints in the step list (e.g. 'after Step 6, run cargo check -p windmill-native-triggers --features native_trigger before starting frontend work') with a fix-and-retry loop, instead of concentrating all validation in the end checklist.

DimensionReasoningScore

Conciseness

The body is dense and Windmill-specific with no explanations of concepts Claude already knows, but it duplicates its own pattern explanations: the two create paths appear in 'Create Lifecycle: Two Paths' and again in 'Skipping update+get After Create (Google Pattern)', and maintain_triggers strategies are covered three times (trait comments, code comments, Special Patterns).

3 / 5

Actionability

Overwhelmingly concrete — exact SQL migrations, a near-complete External trait implementation, exact file paths, and verifiable commands ('cargo check -p windmill-native-triggers --features native_trigger', 'npx svelte-check --threshold error'). Minor gaps keep it below 5: list_all() is a todo!() stub, the down migration and several enum match arms are given as direction only.

4 / 5

Workflow Clarity

Eighteen numbered steps in correct dependency order (migration → enums → backend → frontend → OpenAPI) plus a testing checklist with concrete compile and functional checks. Not 5 because validation checkpoints are consolidated at the end rather than embedded per phase, and there are no error-recovery feedback loops.

4 / 5

Progressive Disclosure

Good in-file structure with clearly signaled pointers to codebase reference implementations ('Reference: Nextcloud module', 'See backend/windmill-native-triggers/src/google/'), but at ~820 lines with no bundle files at all, the full trait API reference, the ~190-line code template, and the OAuth internals are inlined content that belongs in separate reference files.

3 / 5

Total

14

/

20

Passed

Description

62%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 solid third-person description with an explicit 'Use when' clause covering both what and when for a well-defined niche. Its weaknesses are thin action variety (one capability described three ways) and missing the natural synonyms 'webhook'/'push notification' that users of this feature would say.

Suggestions

List the distinct concrete capabilities instead of one action reworded three times, e.g. 'Add native trigger services to Windmill: database migrations, the External trait implementation, OAuth connections, background sync, and the frontend registry and forms.'

Include the natural trigger synonyms users would say — 'webhook' and 'push notification' — in the 'Use when' clause, e.g. 'Use when implementing or modifying webhook- or push-based trigger integrations for services like Nextcloud or Google.'

Name the reference services (Nextcloud, Google) to sharpen distinctiveness against generic trigger or integration skills.

DimensionReasoningScore

Specificity

Names the domain ('native trigger services to Windmill') and actions ('adding', 'implementing or modifying'), but these are variations of a single action rather than several distinct concrete capabilities, and coverage is not comprehensive (no webhooks, OAuth, or sync).

3 / 5

Completeness

Explicitly answers both: 'Guidance for adding native trigger services to Windmill' (what) and 'Use when implementing or modifying native trigger integrations across the backend and frontend' (when). Not 5 because the 'what' lists only one action and the 'when' lacks user-mention-style trigger phrases or synonyms.

4 / 5

Trigger Term Quality

'native trigger', 'trigger integrations', 'Windmill', and 'backend and frontend' are natural terms for this domain, but they are variations of one concept and the common synonyms a user would say — 'webhook' and 'push notification' — are missing.

3 / 5

Distinctiveness Conflict Risk

'native trigger services to Windmill' carves a clear, distinct niche with low conflict risk; minor overlap remains with hypothetical generic webhook-trigger or Windmill-integration skills via the broad 'integrations... backend and frontend' wording.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (824 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/flows)

Warning

Total

14

/

16

Passed

Repository

windmill-labs/windmill

Path

.agents/skills/native-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.