exa-webhooks-events
Implement Exa webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Exa event notifications securely. Trigger with phrases like "exa webhook", "exa events", "exa webhook signature", "handle exa events", "exa notifications".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-webhooks-events78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is that the capability description could be more specific about concrete actions beyond 'validation and event handling'. The explicit trigger phrases and Exa-specific terminology make it highly distinctive.
Suggestions
Expand specificity by listing concrete actions like 'verify HMAC signatures, parse event payloads, handle retry logic, process specific event types'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa webhooks) and some actions (signature validation, event handling), but lacks comprehensive concrete actions like specific validation steps, error handling, or payload processing details. | 2 / 3 |
Completeness | Clearly answers both what (implement webhook signature validation and event handling) and when (setting up webhook endpoints, implementing signature verification, handling event notifications) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'exa webhook', 'exa events', 'exa webhook signature', 'handle exa events', 'exa notifications'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Exa webhooks with distinct triggers. The 'exa' prefix throughout makes it unlikely to conflict with generic webhook skills or other service-specific webhook handlers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code for implementing Exa webhook handling with good security practices (timing-safe comparison, replay protection). However, it could be more concise by removing obvious prerequisites and redundant output sections. The workflow would benefit from explicit validation checkpoints between implementation steps.
Suggestions
Remove the 'Prerequisites' section or reduce it to only non-obvious requirements (the webhook secret configuration is the only truly necessary item)
Add explicit validation steps in the Instructions section, such as 'Step 2b: Test signature verification with a known-good payload before proceeding'
Remove or condense the 'Output' section as it restates what the skill accomplishes rather than providing actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' listing things Claude already knows (understanding of cryptographic signatures) and the 'Output' section which is redundant. The error handling table adds value but could be more compact. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for Express.js webhook setup, signature verification with timing-safe comparison, event handling patterns, and idempotency with Redis. All code is copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | Steps are listed in the 'Instructions' section but lack explicit validation checkpoints. For a security-critical operation like webhook signature verification, there should be explicit 'verify this works' steps between implementation phases. The workflow is present but validation gaps exist. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is somewhat monolithic. The idempotency section could be a separate reference file. References to external resources are present but the internal structure could better separate core vs advanced patterns. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.