validate-trigger

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

Quality

72%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and workflow-clear, with exact paths, flags, and validation checkpoints for a complex audit task. It loses points for not splitting its substantial checklists into bundle files and for some redundancy between the step checklists and the summary.

Suggestions

Move the per-file validation checklists (Steps 3-7) or the severity catalog into reference files under ./references/ and link to them, reducing SKILL.md length and redundancy with the Checklist Summary.

Trim the closing Checklist Summary since it restates the step-level checks already covered above, saving tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence, but the 230-line checklist repeats constraints across Steps 3-7 and the Checklist Summary restates prior sections, so it could be tightened without losing clarity.	2 / 3
Actionability	It provides concrete, specific guidance throughout — exact file paths, exact field/flag names (safeCompare, includeDropdown, extractIdempotencyId), exact verification commands (bun run type-check), and a severity-grouped fix protocol, all copy-paste actionable.	3 / 3
Workflow Clarity	An explicit 8-step sequence with validation checkpoints (WebFetch docs first, Step 8 'Report and Fix' with re-read verification and type-check pass) and a hard 'no guessing' rule for unknown payloads gives clear feedback loops for this risky batch-audit operation.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a single monolithic SKILL.md with no references to separate files; while well-organized by sections, content that could be split (the full severity catalog, the per-file checklists) is kept inline, matching the score-2 anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 distinct within a clear niche, naming concrete actions and reference sources. It is capped by the absence of an explicit 'Use when...' trigger clause and somewhat limited natural keyword coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when auditing or fixing an existing Sim webhook trigger implementation.'

Include natural trigger terms users would say such as 'audit', 'check', 'webhook', or 'provider handler' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the concrete action ('Validate an existing Sim webhook trigger') and two concrete reference sources ('provider API docs and repository conventions'), matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does (validate a trigger against docs and conventions) but has no 'Use when...' clause or explicit trigger guidance, which the guidelines say should cap completeness at 2.	2 / 3
Trigger Term Quality	'webhook trigger', 'provider API docs', and 'repository conventions' are relevant, but it lacks common user-spoken variations like 'webhook', 'audit', or 'check trigger'; closer to 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow domain (Sim webhook trigger validation against provider API docs and repo conventions) is a clear niche unlikely to overlap with other skills.	3 / 3
	Total	10 / 12 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: 6f514c1

Reviewed: about 16 hours 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.