CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate-trigger

Validate an existing Sim webhook trigger against provider API docs and repository conventions

Quality

76%

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/validate-trigger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An exceptionally actionable, well-sequenced audit workflow: every check references concrete files, helpers, commands, or conventions, and the fix phase is gated by explicit validation with a re-verify loop. Its only structural weaknesses are a redundant closing checklist and the absence of any content split across reference files despite the skill's length.

DimensionReasoningScore

Conciseness

The body is dense, checklist-driven prose that assumes Claude's competence — it never explains what webhooks or HMAC are — but the closing "Checklist Summary" (~13 lines) duplicates the step checklists and the Step 8 severity bullets restate earlier items, so it fits 'efficient; minor instances that could be trimmed' rather than the fully lean anchor.

4 / 5

Actionability

Guidance is fully concrete and executable throughout: exact file paths ("apps/sim/lib/webhooks/providers/registry.ts"), copy-paste commands ("bun run type-check", "bun run --cwd apps/sim test lib/webhooks/providers/<handler-basename>" with the kebab/snake-case caveat), exact return shapes ("{ providerConfigUpdates: { externalId } }"), and named helpers ("safeCompare", "resolveEnvVarsInObject", "createHmacVerifier").

5 / 5

Workflow Clarity

The eight steps are clearly sequenced (gather files, pull docs, validate each layer, report, fix) with explicit validation checkpoints (type-check passes, handler tests pass, re-read modified files), a fix-then-verify feedback loop, and per-layer checklists; the no-guessed-payload hard rule even specifies fallback options, matching the top anchor for complex processes.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the one cross-skill reference ("apply the `validate-selector` skill") is clearly signaled, but this is a ~240-line single file with no bundle files — per-layer checklists or the report-format examples could be split into reference files so unneeded sections (e.g., subscriptions for services without them) don't load every run, which keeps it below the 'content appropriately split' anchor.

4 / 5

Total

18

/

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 distinctive about its niche — validating an existing Sim webhook trigger against API docs and repo conventions — and uses appropriate third-person imperative voice. Its main weakness is the absence of any explicit 'when to use' trigger guidance and of natural keyword variations, which leaves a user unsure when to reach for it versus sibling validation skills.

Suggestions

Add an explicit trigger clause, e.g., "Use when validating or auditing an existing Sim webhook trigger, its provider handler, or its block wiring — before merging, after adding a new trigger, or when webhook events fail to fire or parse correctly."

Enumerate the concrete audit actions to lift specificity, e.g., "Verifies signature auth, event matching, formatInput/output alignment, idempotency, subscription lifecycle, and registry wiring, then fixes and reports issues by severity."

Include natural synonyms users would say, such as "audit" or "check", and terms like "webhook handler" alongside "webhook trigger".

DimensionReasoningScore

Specificity

The description names the concrete domain ("Sim webhook trigger") and two validation bases ("provider API docs" and "repository conventions"), but lists only a single action verb ("Validate") rather than the several specific actions it actually covers (auth verification, event matching, output alignment, subscription lifecycle), matching the 'domain plus 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above it.

3 / 5

Completeness

The 'what' is clear ("Validate an existing Sim webhook trigger against provider API docs and repository conventions"), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; it is not a 2 because the 'what' is specific and concrete.

3 / 5

Trigger Term Quality

"webhook trigger", "validate", and "API docs" are relevant natural keywords for this domain, but common variations a user would say — "audit", "check", "review", "webhook handler" — are absent, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Sim webhook trigger" carves out a clear niche with minimal conflict risk against unrelated skills, but there is minor overlap risk with closely related sibling validation skills in the same repo (e.g., the validate-selector skill referenced in the body), so it fits 'mostly distinct; minor overlap risk' rather than the fully distinct anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/validate-trigger/SKILL.md

Reviewed

Table of Contents

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.