add-trigger

Create webhook or polling triggers for a Sim integration

Quality

65%

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%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 body is a high-quality, code-rich instruction skill with strong sequencing, validation checkpoints, and a comprehensive checklist. Its main weakness is monolithic inlining of ~510 lines with no reference files, which leaves progressive disclosure underdeveloped.

Suggestions

Move the full provider-handler and polling-handler reference implementations into separate files under references/ (e.g. HANDLER_EXAMPLE.md, POLLING_EXAMPLE.md) and link to them from SKILL.md to improve progressive disclosure.

Consider extracting the directory-structure map and the behavior-to-method table into a reference doc, keeping SKILL.md as a concise overview + quick-start.

Tighten the opening role-setup paragraph ("You are an expert at...") since Claude does not need that framing to perform the task.

Dimension	Reasoning	Score
Conciseness	Content is dense and assumes Claude's competence with no padding about basic concepts; only minor instances of over-explanation (e.g. the opening "You are an expert..." role setup) could be trimmed.	4 / 5
Actionability	Provides multiple concrete, executable TypeScript examples and specific commands (bun run type-check, generate-docs.ts); minor gaps remain from the {service} template placeholders and `// ...` ellipses in the polling handler.	4 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1-3 plus provider/polling sections) with explicit validation gates (output alignment, "Always verify by checking the output", type-check) and a thorough checklist with error-recovery guidance for unknown payloads.	5 / 5
Progressive Disclosure	Well-sectioned but a single ~510-line monolithic file with no bundle references; substantial material (directory layout, full handler/polling examples) that could be split into reference files is inlined, and there are no external references to signal.	3 / 5
	Total	16 / 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 clear and appropriately scoped but terse: it states the core capability without a "Use when" trigger clause or a fuller enumeration of the actions involved. Adding explicit activation guidance and a few more concrete actions would lift specificity and completeness.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when adding webhook or polling triggers to a Sim integration, or when the user asks to wire up events/notifications for a service block."

Expand the action list to reflect the full workflow, e.g. "Create trigger files, provider/polling handlers, register triggers, and wire them into a block."

Include natural synonyms users might say (events, notifications, integrations) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Create webhook or polling triggers for a Sim integration") but does not enumerate the multiple actions the skill actually covers (register, wire to blocks, handler creation), so it is not comprehensive.	3 / 5
Completeness	Has a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ("webhook", "polling triggers", "triggers", "Sim integration") but misses common natural variations users might say such as "events", "notifications", or integration-related synonyms.	3 / 5
Distinctiveness Conflict Risk	Scoped to a Sim integration's trigger system, giving it a distinct niche with only minor overlap risk against other closely related Sim skills.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (517 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-trigger/SKILL.md
Commit: 804a452

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