documenso-deploy-integration

Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise deployment skill with strong workflow structure via checklists and error-handling feedback. Its main weakness is progressive disclosure: the SKILL.md body duplicates detailed configs that belong in the existing reference file, and that reference file is never linked from the body.

Suggestions

Reference references/implementation-guide.md from the body (e.g., add a '## Full deployment configs' section pointing to it) so the bundle file is discoverable rather than orphaned.

Move the detailed, platform-specific manifests (Docker/Kubernetes/Lambda) out of SKILL.md into the reference, keeping the body a concise overview that links one level deep.

Deduplicate the Dockerfile and docker-compose content between the body and implementation-guide.md to avoid drift; keep a single canonical copy in the reference.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code and minimal prose, with no padding explaining concepts Claude already knows; every section (Dockerfile, compose, Lambda, gcloud, health check) earns its tokens, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts—a complete multi-stage Dockerfile, a docker-compose.prod.yml, a TypeScript Lambda handler, gcloud deploy commands, and a health-check endpoint—matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps are numbered (Step 1–5), and validation/feedback is present via a deployment checklist, a dedicated health-check endpoint step, and an error-handling table mapping issues to causes and solutions, satisfying the 'checklists for complex processes' and 'feedback loops for error recovery' elements of the top anchor.	3 / 3
Progressive Disclosure	The body keeps detailed platform configs inline and the existing bundle file references/implementation-guide.md is never referenced or linked from the body (and largely duplicates its content), fitting the 'references present but not clearly signaled; content that should be separate is inline' anchor rather than the well-signaled one-level-deep top anchor.	2 / 3
	Total	11 / 12 Passed

Description

90%

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 well-constructed description that clearly answers both what the skill does and when to use it, with natural trigger phrases and a distinct, product-specific niche. The only weakness is that the capability verbs are somewhat generic rather than enumerating concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Deploy Documenso integrations') and several actions ('deploying to cloud platforms, containerizing applications, or setting up infrastructure'), but the actions are generic deployment verbs rather than multiple concrete specific operations, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Explicitly states what ('Deploy Documenso integrations across different platforms and environments') and when ('Use when deploying to cloud platforms, containerizing applications...') with explicit trigger phrases, satisfying both halves of the top anchor.	3 / 3
Trigger Term Quality	Provides four natural trigger phrases a user would say ('deploy documenso', 'documenso docker', 'documenso kubernetes', 'documenso cloud deployment'), covering the main platform variations, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a named product (Documenso) with product-specific trigger phrases, giving it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 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: 4 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.