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 well-structured skill description that clearly identifies its niche (Documenso webhook integration), provides explicit trigger terms, and answers both what and when. The main weakness is that the specific capabilities could be more granular—listing concrete actions like configuring endpoints, parsing webhook payloads, or handling specific event types would strengthen specificity.
Suggestions
Add more concrete actions such as 'configure webhook endpoints, parse event payloads, handle document.completed and document.signed events, verify webhook signatures' 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 endpoint creation, payload parsing, signature verification, or retry handling. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement webhook configuration and event handling) and 'when' (setting up webhook endpoints, handling document events, implementing real-time notifications) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'documenso webhook', 'documenso events', 'document completed webhook', 'signing notification'. These cover both product-specific and action-specific phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Documenso' combined with webhook/event handling context. Unlikely to conflict with generic webhook skills or other document signing platform 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 in two languages. Its main weakness is length—providing both TypeScript and Python implementations inline plus detailed payload structures makes it verbose for a single SKILL.md without supporting bundle files. The error handling table and idempotency guidance are strong additions that demonstrate production-readiness awareness.
Suggestions
Extract the Python alternative implementation and the full payload structure into separate bundle files (e.g., PYTHON_HANDLER.md, PAYLOAD_REFERENCE.md) and reference them from the main skill to improve progressive disclosure and reduce token cost.
Remove inline comments that explain obvious intent (e.g., '// All recipients signed -- download final PDF, update CRM') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity—inline comments explaining obvious things ('All recipients signed -- download final PDF, update CRM'), the Python example largely duplicates the TypeScript one, and the events table 'Use Case' column adds marginal value. The payload structure section and error handling table are useful but the overall content could be tightened. | 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 with code. All examples are copy-paste ready with specific headers, routes, and environment variable references. | 3 / 3 |
Workflow Clarity | The six steps are clearly sequenced from dashboard configuration through handler implementation, local testing with ngrok, curl verification, and idempotency. Validation is addressed via the curl test step, secret verification middleware, and the error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table of contents-like flow, but it's quite long for a single file with no bundle files to offload detail into. The Python alternative handler and the full payload structure could reasonably be in separate referenced files. References to external docs and a next-steps link exist but the skill itself is monolithic. | 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
3a2d27d
- 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.