documenso-webhooks-events
Implement Documenso webhook configuration and event handling. Use when setting up webhook endpoints, handling document events, or implementing real-time notifications for document signing. Trigger with phrases like "documenso webhook", "documenso events", "document completed webhook", "signing notification".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-webhooks-events85
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 strong trigger terms and clear when/what guidance. The main weakness is that the capabilities could be more specific - listing concrete actions like parsing payloads, handling specific event types, or configuring webhook settings would strengthen it. Overall, it's a solid description that would enable accurate skill selection.
Suggestions
Add more specific concrete actions such as 'parse webhook payloads', 'handle DOCUMENT_COMPLETED events', 'configure webhook endpoints' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso webhooks) and some actions (configuration, event handling, real-time notifications), but lacks specific concrete actions like 'parse webhook payloads', 'validate signatures', or 'configure retry policies'. | 2 / 3 |
Completeness | Clearly answers both what (implement webhook configuration and event handling) and when (explicit 'Use when...' clause with specific scenarios plus 'Trigger with phrases' providing additional guidance). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'documenso webhook', 'documenso events', 'document completed webhook', 'signing notification'. Good coverage of variations including both technical and user-friendly terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Documenso webhooks specifically. The product name 'Documenso' combined with webhook-specific terminology makes it highly unlikely to conflict with generic webhook or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples and clear workflow steps. The main weakness is length - the extensive event handler implementations and idempotency patterns could be moved to separate reference files to improve progressive disclosure. The content is well-organized but could be more concise by trimming some of the inline comments and consolidating similar patterns.
Suggestions
Move detailed event handler implementations to a separate HANDLERS.md file, keeping only one example handler inline to demonstrate the pattern
Consolidate the two idempotency implementations (Set-based and Redis-based) into a separate file, showing only the Redis production version inline
Remove inline code comments that explain obvious operations (e.g., '// Step 1: Verify webhook secret' when the code is self-explanatory)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as extensive inline code comments and explanations that Claude would understand. The event handlers section could be more condensed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations, specific curl commands for testing, and copy-paste ready examples. The webhook endpoint, event handlers, and idempotency patterns are all concrete and runnable. | 3 / 3 |
Workflow Clarity | Clear 4-step process with explicit validation (Step 1: Verify webhook secret, Step 2: Parse payload, Step 3: Log event, Step 4: Handle event). Includes error handling table and idempotency implementation for preventing duplicate processing. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~300 lines) with extensive inline code that could be split into separate reference files. The event handlers section especially could be moved to a separate file with just the pattern shown inline. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 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.