add-trigger

Create webhook or polling triggers for a Sim integration

Quality

75%

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

77%

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

The body is highly actionable and well-sequenced with strong validation checkpoints for a genuinely complex, multi-file task. Its weak spots are some redundant code examples and a monolithic single-file structure with no progressive disclosure into separate reference files.

Suggestions

Consolidate the duplicated output-schema examples (Step 1's build{Service}Outputs and the standalone "Trigger Outputs Schema" section) into one canonical reference to tighten conciseness.

Split the substantial polling-trigger material into a separate reference file (e.g. POLLING.md) referenced from the main body, so SKILL.md stays an overview and progressive disclosure improves.

Merge or clearly delimit the two overlapping {service}Handler examples (the inline example handler and the createSubscription/deleteSubscription handler) so readers do not mistake them for conflicting definitions.

Dimension	Reasoning	Score
Conciseness	The ~514-line body is mostly lean, project-specific code and patterns (no conceptual padding about what webhooks are), but it carries redundancy — the output schema appears in both Step 1 (build{Service}Outputs) and again in a separate "Trigger Outputs Schema" section, and two separate {service}Handler examples overlap — so it could be tightened, matching the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	It provides fully executable TypeScript code, exact directory structures, precise registry additions, a YAML cron-job snippet, and copy-paste-ready examples for every step, with concrete commands such as `bun run type-check`.	3 / 3
Workflow Clarity	The process is clearly sequenced (Your Task 1-4, then Step 1/2/3, Provider Handler, and a comprehensive Checklist) with explicit verification checkpoints (`bun run type-check passes`, manually verify output keys, verify generate-docs output) and recovery guidance (the "Hard Rule" fallbacks and Output Alignment rules), so batch file-generation work is not left unvalidated.	3 / 3
Progressive Disclosure	The content is well-organized with clear headers, tables, and checklists, but it is a single monolithic ~514-line file with no bundle/reference files, and the large polling section is inline content that could reasonably be split into a separate reference — fitting the anchor where some structure exists but content that should be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 distinct, naming concrete webhook and polling trigger mechanisms for a Sim integration. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness and weakens discoverability.

Suggestions

Add a "Use when..." clause spelling out the natural trigger conditions, e.g. "Use when adding webhook or polling triggers to a Sim integration, or when a service needs event-driven automation."

Expand the action list slightly (e.g. mention registering handlers and wiring triggers to blocks) to lift specificity from a partial list to a comprehensive one.

Include common keyword variations users might say (e.g. "webhooks", "event triggers", "polling triggers") to reinforce trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Create webhook or polling triggers for a Sim integration" names the domain (Sim integration) and two concrete approaches (webhook, polling), but it is not a comprehensive list of actions (e.g. no mention of provider handlers, registration, or block wiring), matching the anchor that names a domain and some actions but is not comprehensive.	2 / 3
Completeness	It states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 (has what, when is missing or only implied).	2 / 3
Trigger Term Quality	It uses natural terms a developer would actually say — "webhook", "polling", "triggers", "Sim integration" — giving good coverage of the keywords a user would voice when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The scope is a clear, narrow niche (creating triggers for a Sim integration) with distinct trigger-oriented terms, making it unlikely to fire for an unrelated skill.	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 (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: 6f514c1

Reviewed: about 16 hours 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.