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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 with executable code and a clear sequenced workflow, but it is somewhat redundant across languages and its progressive disclosure is misaligned — the provided reference file is unlinked and inline content duplicates it.

Suggestions

Link the existing references/implementation-guide.md from the body and move the duplicated event table / setup detail there instead of keeping two full handler implementations inline.

Drop one of the redundant TypeScript/Python verification examples, or move the second language into the reference file, to reduce token cost.

Fix the Python example's missing 'import os' (it uses os.environ without importing os) so the code is actually executable.

Dimension	Reasoning	Score
Conciseness	The body is task-focused rather than padded with concepts Claude knows, but it includes redundant full handler implementations in both TypeScript/Express and Python/Flask demonstrating the same shared-secret verification, so it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready executable code, concrete curl/ngrok commands, a full payload structure, and an error-handling table — concrete and specific rather than abstract.	3 / 3
Workflow Clarity	Six steps are clearly sequenced (create webhook, handler, verification, local dev, test, idempotency) with a secret-verification checkpoint and an error-handling table for recovery, satisfying the explicit-validation anchor.	3 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists but is never linked from the body, while the body links to documenso-install-auth and documenso-performance-tuning which are not present; the ~240-line body keeps full implementations inline rather than splitting them out.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities, gives an explicit 'Use when' clause, and lists natural trigger phrases. It clearly distinguishes the skill and is unlikely to conflict with others.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Implement Documenso webhook configuration and event handling', 'setting up webhook endpoints', 'handling document events', 'implementing real-time notifications' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' (implement webhook configuration and event handling) and 'when' ('Use when setting up webhook endpoints, handling document events...') with explicit trigger guidance, matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say — 'documenso webhook', 'documenso events', 'document completed webhook', 'signing notification' — giving good coverage of natural terms rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Documenso webhooks) with brand-specific triggers unlikely to fire for unrelated skills, matching the distinct-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 2 days 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.