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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 solid skill description that clearly identifies its niche (Documenso webhook integration), provides explicit trigger guidance, and answers both what and when. Its main weakness is that the specific capabilities could be more granular—listing concrete actions like parsing webhook payloads, verifying webhook signatures, or handling specific event types would strengthen the specificity dimension.
Suggestions
Add more concrete actions such as 'register webhook endpoints, parse event payloads, verify webhook signatures, handle document.completed and document.signed events' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso webhooks) and some actions (webhook configuration, event handling, real-time notifications), but doesn't list multiple concrete specific actions like registering endpoints, parsing payloads, verifying signatures, or handling specific event types. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement webhook configuration and event handling for Documenso) and 'when' (setting up webhook endpoints, handling document events, real-time notifications for document signing), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'documenso webhook', 'documenso events', 'document completed webhook', 'signing notification'. These are terms users would naturally use when needing this functionality, and the explicit trigger phrase list is helpful. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Documenso webhooks specifically. The combination of 'Documenso' + 'webhook' + 'document signing' creates a clear, distinct trigger space that is unlikely to conflict with other 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, highly actionable skill with clear step-by-step workflow and executable code examples in two languages. Its main weakness is length — providing both TypeScript and Python implementations inline makes it verbose, and some content could be split into referenced files. The error handling table and idempotency guidance are strong additions that demonstrate production-readiness awareness.
Suggestions
Move the Python implementation to a separate referenced file (e.g., `documenso-webhooks-python.md`) to reduce inline bulk and improve progressive disclosure.
Trim inline code comments that restate what the code obviously does (e.g., '// All recipients signed -- download final PDF, update CRM') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity — the Python example largely duplicates the TypeScript handler, the comment-heavy code could be tighter, and some explanatory text (e.g., describing what each event does in the table's 'Use Case' column) adds moderate bloat. The overview section is concise, but overall it could be trimmed. | 2 / 3 |
Actionability | Provides fully executable TypeScript and Python webhook handlers, a concrete curl test command with realistic payload, ngrok setup instructions, and an idempotency pattern. Code is copy-paste ready with specific headers, routes, and environment variable references. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced from dashboard setup through handler implementation, local testing with ngrok, curl verification, and idempotency. Validation is present via the curl test step and the error handling table provides a feedback loop for common failure modes. The 'acknowledge immediately, process async' pattern is explicitly called out. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table of contents-like flow, but it's quite long (~180 lines of substantive content) with both TypeScript and Python implementations inline. The Python handler could be referenced as a separate file. References to external docs and next steps are present but the main file carries a lot of inline detail. | 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 | |
- Commit
70e9fa4
- 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.