native-trigger

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

Quality

63%

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

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.

This is a thorough, highly actionable implementation guide with concrete backend code and a clear step sequence. Its main weaknesses are length/repetition and a monolithic structure with no external reference files despite the large volume of inlined templates.

Suggestions

Move the full External-trait reference and the per-service reference-implementation tables into separate one-level-deep reference files (e.g., REFERENCE.md, EXAMPLES.md) linked from the overview.

De-duplicate the Google/create-lifecycle material between Core Concepts and Special Patterns, keeping the latter only for deviations.

Add `cargo check` / `svelte-check` validation as an explicit checkpoint after the backend and frontend step groups rather than only in the final checklist.

Dimension	Reasoning	Score
Conciseness	Content is domain-dense and assumes Claude's competence (no basic Rust/OAuth primers), but at ~790 lines it repeats the Google/create-lifecycle patterns across Core Concepts and Special Patterns and could be tightened.	3 / 5
Actionability	Backend steps supply full executable Rust and SQL code with concrete file paths, but the frontend steps (7-16) give high-level "update X, Y, Z" direction without code, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly sequenced 18-step guide plus an explicit testing checklist provides solid validation, but checks live in a final block rather than as interleaved checkpoints within the flow.	4 / 5
Progressive Disclosure	Sections and tables are well organized, but the skill is a monolithic ~790-line SKILL.md with no bundle files; reference implementations and full code templates are inlined rather than split into one-level-deep 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.

The description clearly communicates a specific niche and includes an explicit Use-when trigger, satisfying the core completeness bar. It is held back from the top tier by limited action specificity and sparse trigger-term variation.

Suggestions

List 2-3 more concrete actions (e.g., "register webhooks, manage OAuth tokens, wire frontend trigger forms") to lift specificity.

Add natural trigger synonyms a user might say (e.g., "when the user asks to add a webhook trigger or push-notification integration to Windmill").

Expand the Use-when clause with a couple of concrete phrasings to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("native trigger services to Windmill") and 1-2 concrete actions ("adding", "implementing or modifying"), but does not enumerate multiple specific actions, so it is not comprehensive.	3 / 5
Completeness	Explicitly states what ("Guidance for adding native trigger services to Windmill") and when ("Use when implementing or modifying native trigger integrations across the backend and frontend"), but the when clause could list a broader set of concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant natural terms ("native trigger", "Windmill", "backend and frontend", "integrations") but repeats "native trigger" and lacks synonyms or variations a user might phrase differently.	3 / 5
Distinctiveness Conflict Risk	The Windmill native-trigger niche is specific and unlikely to fire for unrelated skills, with only minor overlap risk against general webhook/trigger-integration skills.	4 / 5
	Total	14 / 20 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: 2fb7903

Reviewed: 4 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.