validate-trigger

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

Quality

61%

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

70%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 well-sequenced, highly actionable audit workflow with strong validation checkpoints and a fix-then-verify feedback loop, scoring top marks on workflow clarity. Its weaknesses are conciseness (redundant recap sections) and progressive disclosure (no bundle files and heavy inline detail that could be externalized).

Suggestions

Remove or collapse the redundant "Checklist Summary" and the Report Format severity re-lists, since they restate checkboxes already covered in Steps 3-7, to tighten token efficiency.

Move the lengthy per-area specification lists (e.g., formatInput and auth-verification rules) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add a brief "Quick start" overview at the top summarizing the 8 steps before the detailed checklists, so the high-level workflow is scannable without loading the full detail.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but it is ~223 lines with genuine padding — the final "Checklist Summary" and the Report Format severity lists restate items already enumerated as checkboxes in Steps 3-7, fitting the anchor for mostly-efficient content that could be tightened rather than the noticeably-verbose level 2.	3 / 5
Actionability	For an instruction-only skill the guidance is highly concrete: exact file paths, named functions/fields (verifyAuth, matchEvent, formatInput, safeCompare), exact return shapes ({ input: { ... } }, { providerConfigUpdates: { externalId } }), and runnable commands (bun run type-check, bun test {service}), matching mostly-executable guidance with only minor gaps; it stops short of 5 because it offers checklists rather than copy-paste runnable code.	4 / 5
Workflow Clarity	An explicit 8-step sequence is paired with validation checkpoints and a feedback loop in Step 8 (fix, then confirm type-check/tests pass and re-read modified files before proceeding), plus the "No Guessed Webhook Payload Schemas" guard and per-area checklists for a complex destructive/batch process — matching the anchor for clear sequence, explicit validation, and error-recovery feedback loops.	5 / 5
Progressive Disclosure	No bundle files exist and everything is inline in a ~223-line SKILL.md with no one-level references, so substantial per-area detail (formatInput rules, auth verification specs) that could live in separate reference files is inlined; the in-file section structure is clear but there is no file-level disclosure or reference signaling, fitting the some-structure anchor rather than the 4 or 5 that require signaled references.	3 / 5
	Total	15 / 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 concrete and domain-specific with a clear single purpose, but it omits any "Use when..." trigger guidance and lacks natural keyword variations, capping completeness and trigger-term quality at the midpoint. It is distinct as a niche but would benefit from explicit activation phrasing.

Suggestions

Add a "Use when..." clause (e.g., "Use when validating or auditing an existing Sim webhook trigger against its provider's API docs") to satisfy the "when" half of completeness and raise the cap.

Broaden trigger-term coverage with natural phrasings and synonyms users would actually say, such as "webhook", "validate a webhook trigger", and "audit trigger wiring".

Optionally enumerate two or three concrete actions (e.g., "validate auth, formatInput, and subscription lifecycle") to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ("Sim webhook trigger") and one main action ("Validate ... against provider API docs and repository conventions"), matching the anchor that names a domain with 1-2 concrete actions but not comprehensive coverage; it does not list several distinct actions to reach a 4.	3 / 5
Completeness	The description gives a clear "what" (validate an existing Sim webhook trigger) but no "when"/"Use when..." clause at all, which per the guidelines caps completeness at 3; it is not a 4 because the "when" is fully absent rather than merely less explicit.	3 / 5
Trigger Term Quality	Terms like "Validate", "webhook trigger", "provider API docs", and "repository conventions" are domain-accurate but lean technical with no synonyms or natural user phrasings (e.g., "validate a webhook"), fitting the anchor for some relevant keywords missing common variations rather than good coverage at 4.	3 / 5
Distinctiveness Conflict Risk	"Sim webhook trigger" is a clear, specific niche with only minor overlap risk against closely related audit/lint skills, fitting the mostly-distinct anchor; it stops short of 5 because there are no explicit trigger phrases that would make conflict risk minimal in practice.	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: 417ae20

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.