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".
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), provides explicit trigger guidance, and answers both what and when questions. Its main weakness is that the specific capabilities listed are somewhat generic deployment terms rather than highly concrete actions. The inclusion of explicit trigger phrases is a strong point that aids skill selection.
Suggestions
Add more specific concrete actions such as 'write 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 'configure Kubernetes manifests' or 'build Docker images'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (deploy Documenso integrations across platforms and environments) and 'when' (explicit 'Use when' clause for cloud platforms, containerizing, infrastructure setup, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | The description includes explicit trigger phrases that users would naturally say: 'deploy documenso', 'documenso docker', 'documenso kubernetes', 'documenso cloud deployment'. It also includes natural terms like 'cloud platforms', 'containerizing applications', and 'infrastructure'. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Documenso' as a specific product name with deployment-specific triggers like 'documenso docker' and 'documenso kubernetes' creates a clear niche that is unlikely to conflict with generic deployment skills or other integration skills. | 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 deployment skill with excellent actionability—every deployment target has concrete, executable code. The main weaknesses are the lack of explicit validation/verification steps between deployment stages (e.g., confirming builds succeed, testing endpoints post-deploy) and the lengthy inline configurations that could benefit from progressive disclosure. The deployment checklist partially compensates but doesn't integrate into the workflow as explicit checkpoints.
Suggestions
Add explicit validation steps after each deployment stage (e.g., 'Run `docker build` and verify exit code 0', 'After deploy, curl the health endpoint to confirm connectivity')
Move the Docker Compose production config and Lambda handler into separate referenced files to reduce inline bulk and improve progressive disclosure
Remove the Prerequisites section—Claude doesn't need to be told to have Docker installed or a cloud account ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable examples, but includes some unnecessary elements like the 'Prerequisites' section listing obvious items and the 'Overview' paragraph that restates what the skill does. The Docker Compose config is quite lengthy and could reference Documenso's official compose file instead of inlining everything. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code across multiple deployment targets: Dockerfile, Docker Compose, Lambda handler, Cloud Run commands, and health check endpoint. Specific commands like `gcloud secrets create` and `gcloud run deploy` with concrete flags are included. | 3 / 3 |
Workflow Clarity | Steps are clearly 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' or 'test the health endpoint after deployment'). For deployment operations which can be destructive, feedback loops are missing. | 2 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and a reference to `documenso-webhooks-events` for next steps. However, the Docker Compose and Lambda sections are quite long inline content that could be split into separate reference files. The external resource links at the end are helpful but the main body is somewhat monolithic. | 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 | |
- Commit
3e83543
- 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.