validate-trigger

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/validate-trigger/SKILL.md

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.

The body is a highly actionable, well-sequenced audit workflow with explicit validation checkpoints and concrete file paths/commands, weakened only by minor redundancy in the anti-guessing rule and report-example sections. It is a strong instruction-only skill that needs no code to score well on actionability.

Suggestions

Condense the four 'Do NOT' lines under 'No Guessed Webhook Payload Schemas' into a single sentence with a bulleted inline list to recover tokens.

Trim the report-format severity examples to one representative item per severity level instead of listing several per bucket.

Consider moving the long per-area checkbox clusters (provider handler, subscription lifecycle) into a reference file referenced from the main flow to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a dense checklist of concrete, project-specific checks that mostly earns its tokens, but the 'Hard Rule' section repeats four near-identical 'Do NOT' lines and the report-format severity examples could be trimmed, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Every step names exact file paths, interface contracts, and copy-paste-ready commands (e.g. 'bun run type-check', 'bun run --cwd apps/sim test lib/webhooks/providers/<handler-basename>'), giving fully executable guidance that covers the common validation cases.	5 / 5
Workflow Clarity	An explicit 8-step sequence runs from gathering files through reporting and fixing, with a final validation block (type-check, re-read modified files, run handler tests, report unknown schemas) that provides the validate-fix-retry feedback loop required for a batch audit-and-fix operation.	5 / 5
Progressive Disclosure	Content is organized into clearly headed steps with a checklist summary and a single well-signaled cross-skill reference ('apply the validate-selector skill'); no bundle files exist to split further, and the inline per-area checklists belong to one coherent sequential workflow, leaving only minor organization gaps.	4 / 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 distinguishable but lacks any explicit 'when to use' trigger guidance, which caps its completeness and limits trigger-term quality. Adding a 'Use when...' clause with natural trigger phrases would lift the two weaker dimensions.

Suggestions

Append a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when auditing or fixing a Sim webhook trigger, or when the user asks to validate webhook provider wiring.'

Add common synonyms/extensions users might say (e.g. 'webhook handler', 'provider registry', 'signature verification') to broaden trigger-term coverage.

Optionally expand the action list to surface the concrete validation areas (auth verification, formatInput alignment, subscription lifecycle) for fuller capability specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Sim webhook trigger') and one concrete action ('Validate') qualified by two reference bases ('provider API docs and repository conventions'), but does not enumerate multiple specific validation actions, so it stops at the domain-plus-1-2-actions anchor.	3 / 5
Completeness	It clearly states what the skill does ('Validate an existing Sim webhook trigger against provider API docs and repository conventions') but entirely omits any 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords like 'webhook trigger', 'provider API docs', and 'Sim' are present, but there are no synonyms, file extensions, or natural phrase variations a user might say, fitting the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Sim webhook trigger' niche is specific and largely distinct from other skills, with only minor overlap risk against a generic webhook-validation skill, placing it just below the clear-niche-minimal-conflict anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
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
Commit: 7945b29

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.