CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-trigger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, highly actionable skill: complete code templates, exact registration targets, an enforced no-guessing rule, and unusually thorough validation via check scripts and a checklist. The main improvements are tightening a few long templates and splitting the polling and provider-handler detail into reference files.

DimensionReasoningScore

Conciseness

Nearly every token is project-specific (registries, helpers, check scripts, helm values) with no explanation of concepts Claude already knows, but the persona opener "You are an expert at creating webhook and polling triggers for Sim. You understand the trigger system..." and a few long code templates (e.g., the full createSubscription/deleteSubscription example) could be trimmed.

4 / 5

Actionability

The body provides copy-paste TypeScript templates, exact file paths, and runnable commands ("bun run check:cron-parity", "bun run scripts/generate-docs.ts", helm YAML), with only minor gaps: the polling handler elides its core logic ("// Fetch changes since last poll, process with idempotency") and the secondary trigger is sketched as "// Same as above but: ...".

4 / 5

Workflow Clarity

The workflow is clearly sequenced (numbered "Your Task", Steps 1-3, "Registration (3 places)") with explicit validation steps and checklists: "bun run type-check passes", "Always verify by checking the output after running the script", cron-parity and docs checks, plus error-handling guidance like "Throw from createSubscription — orchestration rolls back the DB webhook".

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-sectioned with clearly signaled pointers to reference implementations ("Simple: apps/sim/lib/webhooks/polling/rss.ts", "Complex... gmail.ts") and sibling skills (add-block, add-selector), but the ~550-line monolith inlines webhook, provider-handler, and polling detail that could be split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

61%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 concise and names a specific niche with two concrete actions, but it lacks any 'when to use' guidance and offers only modest keyword coverage. Adding a Use-when clause and a couple of natural trigger phrases would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding webhooks, event triggers, or polling to a Sim integration or when a workflow should start on an external event."

Broaden natural trigger terms with synonyms users actually say, such as "events", "notifications", or "start a workflow when...".

Mention the fuller scope of the task (registration, wiring triggers to blocks, provider handlers) to raise specificity beyond the current two actions.

DimensionReasoningScore

Specificity

"Create webhook or polling triggers for a Sim integration" names the domain (Sim integrations) and two concrete actions (webhook and polling triggers), matching the anchor for 1-2 concrete actions rather than the several specific actions required for a 4.

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 judging guidelines.

3 / 5

Trigger Term Quality

"webhook", "polling", and "triggers" are natural terms users would say for this task, giving good keyword coverage, though common variations like "events", "notifications", or "when a form is submitted" are missing.

4 / 5

Distinctiveness Conflict Risk

"for a Sim integration" establishes a clear niche that is mostly distinct, with only minor overlap risk against closely related Sim skills such as the referenced add-block skill; the lack of explicit trigger guidance keeps it below a 5.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (549 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

Revision

6c0e6ee

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill