documenso-multi-env-setup
Configure Documenso across multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows. Trigger with phrases like "documenso environments", "documenso staging", "documenso dev setup", "multi-environment documenso".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-multi-env-setup/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 well-structured skill description that clearly identifies its niche (Documenso multi-environment configuration) and provides explicit trigger guidance. The 'Use when' and 'Trigger with phrases' sections are strong. The main weakness is that the specific capabilities could be more concrete—listing actual configuration actions rather than somewhat generic terms like 'managing API keys' and 'environment-specific configurations'.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Configure database URLs, SMTP settings, webhook endpoints, and signing certificates per environment' instead of the more generic 'environment-specific configurations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso multi-environment configuration) and some actions (setting up configurations, managing API keys, implementing promotion workflows), but the actions are somewhat generic and not deeply specific to concrete operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Documenso across multiple environments, manage API keys, implement promotion workflows) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'documenso environments', 'documenso staging', 'documenso dev setup', 'multi-environment documenso', plus natural keywords like 'API keys', 'environment promotion workflows', 'dev', 'staging', 'production'. Good coverage of terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Documenso' combined with multi-environment configuration focus. Very unlikely to conflict with other skills given the narrow, product-specific niche. | 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, actionable skill with concrete code examples and good environment architecture visualization. Its main weaknesses are the lack of validation checkpoints in the multi-step workflow (especially around production operations and template promotion) and the monolithic structure that inlines all code rather than leveraging bundle files for progressive disclosure. The content could also be tightened by removing some of the more obvious patterns that Claude would already know.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify API key connectivity: curl -H "Authorization: Bearer $DOCUMENSO_API_KEY" $DOCUMENSO_BASE_URL/documents' before proceeding to client factory setup.
Add a verify/rollback step to the template promotion workflow (Step 5) — e.g., create template, verify field positions, then confirm or delete.
Move the larger code blocks (factory.ts, mock.ts, guards.ts) into bundle files and reference them from SKILL.md to improve progressive disclosure and reduce inline bulk.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements — the ASCII architecture diagram is helpful but verbose, and some code blocks (like the full mock client) could be trimmed. The environment checklist table and error handling table add value but the overall document is longer than strictly necessary for the concepts conveyed. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with concrete file paths, complete function implementations, and specific environment variable names. The .env file examples, client factory, guards, and mock client are all copy-paste ready with clear usage patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (1-5), but there are no explicit validation checkpoints between steps. For a multi-environment setup involving production secrets and environment promotion — which are potentially destructive operations — there should be verification steps (e.g., 'verify API key works before proceeding', 'test webhook connectivity'). The template promotion script (Step 5) lacks a validate-then-apply feedback loop. | 2 / 3 |
Progressive Disclosure | The content references external skills (`documenso-install-auth`, `documenso-observability`) which is good, but the SKILL.md itself is monolithic — all code examples are inline rather than split into referenced files. The mock client, factory, and guards could each be separate bundle files with the SKILL.md providing an overview and navigation. | 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
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.