add-trigger

Create webhook or polling triggers for a Sim integration

Quality

69%

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/add-trigger/SKILL.md

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.

The content is highly actionable and clearly sequenced with strong validation checkpoints and checklists, but it is a single large inlined file with no progressive-disclosure bundle structure to offload detail, which is its main weakness.

Suggestions

Move the large reference material (full polling handler + cron job + Helm/values config, provider handler examples) into a references/ file (e.g. POLLING.md, WEBHOOK_HANDLER.md) and link one level deep from SKILL.md to improve progressive disclosure.

Trim redundant restatements of registration steps (the 'Register and Wire' and checklist both enumerate the 3 polling-registration sites) to tighten conciseness toward a 5.

Consider extracting the 'When to Create a Handler' behavior table into a separate reference so the core workflow stays lean while the decision matrix remains discoverable.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence with minimal concept re-explanation, but at ~510 lines there are sections (e.g. the full polling handler + cron job + registration) that could be tightened or moved, keeping it just below the lean 'every token earns its place' anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready TypeScript/YAML is provided for both webhook and polling paths, covering the common cases (utils, triggers, handler, subscription, registration), matching the fully-executable anchor.	5 / 5
Workflow Clarity	The process is explicitly sequenced (Step 1-3, Provider Handler, Polling), reinforced by a comprehensive Checklist, and includes explicit validation/verify guidance ('Output Alignment (Critical)', 'Always verify by checking the output after running the script'), satisfying the clear-sequence-with-checklists anchor.	5 / 5
Progressive Disclosure	The file is well-sectioned by headers but monolithic: no bundle files exist in references/scripts/assets, and substantial content (polling handler, provider handler details) that could live one level deep is inlined rather than split, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	17 / 20 Passed

Description

53%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 specific and uses third-person action voice, but it omits any explicit 'Use when' trigger guidance and relies on a narrow set of technical keywords, leaving it mid-pack on completeness and trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding webhook or polling triggers to a Sim integration, or when a user mentions events, notifications, or polling for a service.'

Broaden trigger terms with natural synonyms (e.g. 'events', 'notifications', 'integration triggers') so the description matches phrasings users actually say.

Optionally name a concrete capability beyond 'create' (e.g. register, wire to blocks, auto-subscribe) to lift specificity toward a 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('triggers for a Sim integration') and two concrete actions ('webhook' and 'polling triggers') but offers no broader coverage of what those entail, matching the anchor that lists 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	The 'what' is clear ('Create webhook or polling triggers for a Sim integration') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant technical keywords ('webhook', 'polling triggers', 'Sim integration') are present, but common natural variations or synonyms a user might say ('event', 'notification', 'integration trigger') are missing.	3 / 5
Distinctiveness Conflict Risk	The Sim-specific webhook/polling-trigger niche is mostly distinct with only minor overlap risk against other Sim integration skills; it is not yet at the clear-niche-with-minimal-conflict level of a 5.	4 / 5
	Total	13 / 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 (514 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-trigger/SKILL.md
Commit: 417ae20

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