documenso-local-dev-loop
Set up local development environment and testing workflow for Documenso. Use when configuring dev environment, setting up test workflows, or establishing rapid iteration patterns with Documenso. Trigger with phrases like "documenso local dev", "documenso development", "test documenso locally", "documenso dev environment".
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-local-dev-loop/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 with excellent trigger terms and completeness, clearly scoped to Documenso local development. Its main weakness is that the capability descriptions are somewhat generic development terms rather than listing specific concrete actions (e.g., database setup, Docker configuration, running specific test commands). The explicit trigger phrases and 'Use when' clause make it highly functional for skill selection.
Suggestions
Add more specific concrete actions like 'configure Docker containers, set up PostgreSQL database, run Playwright tests, configure environment variables' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso local development) and some actions ('configuring dev environment', 'setting up test workflows', 'establishing rapid iteration patterns'), but these are somewhat generic development concepts rather than concrete specific actions like 'install dependencies, configure database, run test suite'. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up local development environment and testing workflow for Documenso) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'documenso local dev', 'documenso development', 'test documenso locally', 'documenso dev environment'. These are natural, specific, and cover common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Documenso' combined with 'local development environment' and 'testing workflow'. Unlikely to conflict with other skills unless there are multiple Documenso-related 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, highly actionable skill with complete, executable code examples covering the full local dev setup workflow. Its main weaknesses are the lack of explicit validation checkpoints between steps (especially around Docker readiness and environment verification) and the monolithic structure that could benefit from splitting detailed configs into bundle files. The content is slightly verbose with repetitive env file examples but generally well-organized.
Suggestions
Add explicit validation checkpoints between steps — e.g., after Step 4 (Docker), include a 'wait for healthy' check before proceeding, and after Step 2 (env config), suggest running the verify script before writing more code.
Extract the docker-compose.local.yml and longer code files into bundle files, referencing them from the SKILL.md to reduce inline bulk and improve progressive disclosure.
Consolidate the three .env examples into a single template with comments indicating which values change per environment, reducing repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The project structure tree, multiple env file examples, and the full docker-compose file add bulk. Some of this is justified (docker-compose is copy-paste ready), but the env files are repetitive and the client wrapper includes a dev helper that could be trimmed. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes fully executable, copy-paste ready code: TypeScript files, docker-compose YAML, bash commands, and package.json scripts. The verification script includes error handling with specific status code checks. All code is complete and runnable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints between steps. The cleanup script handles destructive operations (deleting documents) with a safety check on status, which is good, but the overall workflow lacks a 'verify before proceeding' pattern — e.g., after Docker setup there's no validation that the database is ready, and after env configuration there's no check before moving to the client wrapper step. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a helpful error table, but it's monolithic — all content is inline in a single file with no bundle files to offload detail. The docker-compose config and multiple code files could be split into referenced files. The 'Next Steps' reference to `documenso-sdk-patterns` is good but the Resources section links are external only. | 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.