native-trigger

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

Quality

76%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The skill body is highly actionable and well-sequenced, with complete executable code, exact paths, and validation checkpoints throughout an 18-step workflow. Its weaknesses are conciseness (significant repetition of the same patterns across multiple sections) and progressive disclosure (a monolithic single file with no reference files despite being large enough to benefit from them).

Suggestions

Consolidate the repeated Google/Nextcloud create-path and sync-pattern explanations — they appear in Core Concepts, the step-by-step guide, and Special Patterns; explain each once and cross-reference.

Split detailed reference material (the full External trait signature, the Nextcloud/Google reference tables, the ServiceName method table) into files in a references/ directory and link to them from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and mostly assumes competence (Rust trait snippets, SQL migrations, exact paths), but at ~31KB it is long and includes repeated explanations of the same patterns (e.g., the Google/Nextcloud create paths explained in Core Concepts, the Step-by-Step guide, and Special Patterns again), which could be tightened.	2 / 3
Actionability	It provides complete, executable code blocks (the full External trait impl, SQL migrations, Rust structs, TypeScript config), exact file paths, and concrete commands like `cargo check -p windmill-native-triggers --features native_trigger` and `npm run generate-backend-client`, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The 18-step implementation guide is clearly sequenced, with a final testing checklist that serves as validation checkpoints; destructive/batch operations (DB enum changes, delete handling) are accompanied by explicit verification steps (cargo check, svelte-check), matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	There are no bundle reference files (no references/, scripts/, or assets/), so all content lives inline in a single large monolithic SKILL.md (~31KB) that could be split into reference files (e.g., the trait reference, the Google/Nextcloud reference tables), matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 well-structured, third-person, and explicitly covers both what the skill does and when to use it, with a clear distinctive niche. Its main weakness is specificity and trigger-term breadth — it states the domain rather than enumerating concrete actions and omits natural terms like 'webhook', 'push notifications', and named services.

Suggestions

Add concrete actions to the description, e.g. 'implement the External trait, add database migrations, register backend routes, and build frontend trigger forms'.

Include natural trigger terms users would actually say, such as 'webhook', 'push notifications', 'Google Drive', 'Nextcloud', or 'add a native trigger'.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ('adding native trigger services to Windmill' across 'backend and frontend') but lists only the broad activity rather than multiple specific concrete actions (e.g., defining the External trait, adding DB migrations, registering routes), matching the anchor 'Names domain and some actions, but not comprehensive'.	2 / 3
Completeness	It explicitly answers both what ('Guidance for adding native trigger services to Windmill') and when ('Use when implementing or modifying native trigger integrations across the backend and frontend'), satisfying the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	It includes relevant terms ('native trigger', 'Windmill', 'backend and frontend', 'implementing or modifying native trigger integrations'), but lacks common natural variations a user might say (e.g., 'webhook', 'push notifications', 'Google Drive', 'Nextcloud', 'add a trigger'), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and distinctive ('native trigger services to Windmill ... across the backend and frontend'), with explicit triggers unlikely to overlap with unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (794 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: windmill-labs/windmill
Path: .agents/skills/native-trigger/SKILL.md
Commit: 33d2845

Reviewed: 2 days 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.