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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-deploy-integration/SKILL.mdQuality
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 deployment) and provides explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat generic deployment terms rather than highly specific actions. The explicit trigger phrases and 'Use when' clause make it effective for skill selection.
Suggestions
Add more specific concrete actions such as 'create Dockerfiles, configure Kubernetes manifests, set up CI/CD pipelines, configure environment variables' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Documenso integrations deployment) and mentions some actions (deploying to cloud platforms, containerizing applications, setting up infrastructure), but these are somewhat generic deployment concepts rather than highly specific concrete actions like 'create Dockerfile', 'configure Kubernetes manifests', or 'set up CI/CD pipelines'. | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy Documenso integrations across platforms and environments) and 'when' (deploying to cloud platforms, containerizing applications, setting up infrastructure) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms that users would actually say: 'deploy documenso', 'documenso docker', 'documenso kubernetes', 'documenso cloud deployment'. Also includes broader terms like 'cloud platforms', 'containerizing applications', and 'infrastructure'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Documenso' with deployment-specific terms like 'docker', 'kubernetes', and 'cloud deployment' creates a clear niche. This is unlikely to conflict with general deployment skills or other Documenso skills (e.g., development or configuration) due to the explicit deployment focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 deployment skill with complete, executable code examples across multiple platforms. Its main weaknesses are the lack of integrated validation checkpoints within the deployment workflow (e.g., build verification, smoke testing steps) and the monolithic structure that could benefit from splitting platform-specific guides into separate files. The content is mostly concise but could trim some boilerplate sections.
Suggestions
Add explicit validation steps between workflow stages, e.g., 'docker build and verify: docker run --rm <image> node -e "console.log('ok')"' before pushing, and 'curl /health after deployment to verify connectivity'.
Split platform-specific deployment guides (AWS Lambda, GCP Cloud Run, self-hosted Docker Compose) into separate referenced files, keeping SKILL.md as a concise overview with links to each platform guide.
Remove the Prerequisites section (Claude can infer these) and trim the Overview paragraph to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like the 'Prerequisites' section listing obvious items, and the 'Overview' paragraph that restates what the title already conveys. The Docker Compose example is quite lengthy and could be trimmed, though the inline comments add value. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes fully executable, copy-paste-ready code: a complete multi-stage Dockerfile, a production Docker Compose file, a Lambda handler with secrets management, Cloud Run deployment commands, and a health check endpoint. Specific environment variables and commands are provided rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, and the deployment checklist serves as a validation checkpoint. However, there are no explicit validation/verification steps between stages (e.g., 'verify the container builds successfully before proceeding', 'test the health endpoint after deployment'), and no feedback loops for error recovery during the deployment process itself. The error handling table is reactive rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The content has reasonable structure with clear sections and a reference to `documenso-webhooks-events` for next steps. However, the Docker Compose and multiple deployment platform examples make this quite long; the AWS Lambda, GCP Cloud Run, and self-hosted sections could be split into separate files with the SKILL.md serving as an overview pointing to platform-specific guides. External resource links are provided but inline content is heavy. | 2 / 3 |
Total | 9 / 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 | |
3a2d27d
Table of Contents
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.