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 that clearly identifies its niche (Documenso local development setup) and provides explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat generic development terms rather than listing specific concrete actions the skill performs. The explicit trigger phrases and 'Use when' clause make it highly functional for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Configures Docker containers, sets up database migrations, installs dependencies, and runs test suites for Documenso' instead of generic phrases like 'establishing rapid iteration patterns'.
| 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 concrete trigger 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 and a logical step-by-step structure for setting up a Documenso dev environment. Its main weaknesses are the lack of explicit validation checkpoints between workflow steps (especially after Docker setup and environment configuration) and the monolithic nature of the content that could benefit from splitting detailed configurations into referenced files.
Suggestions
Add explicit validation checkpoints after key steps — e.g., after Step 4 (Docker setup), instruct to run the verify script before proceeding, and after Step 2 (env config), suggest checking that env vars are loaded correctly.
Consider moving the docker-compose.local.yml and detailed script contents into referenced files (e.g., 'See [docker-compose.local.yml](docker-compose.local.yml)') to keep SKILL.md as a concise overview with navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code and clear structure, but includes some unnecessary elements like the 'Overview' paragraph restating what the skill does, and the project structure could be more tightly presented. The env file examples with placeholder values add some bulk but are useful for clarity. | 2 / 3 |
Actionability | Highly actionable with fully executable TypeScript code, complete docker-compose configuration, concrete package.json scripts, and specific environment variable examples. Every step provides copy-paste ready code or commands. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-7) and logically ordered, but there are no explicit validation checkpoints between steps. The cleanup script handles destructive operations (deletion) with a safety check on status, but the overall workflow lacks a 'verify before proceeding' pattern — e.g., after Docker setup there's no explicit validation step before moving to the client wrapper, and the verification script is Step 5 rather than being positioned as a checkpoint after environment setup. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a helpful error handling table, but it's quite long (~180 lines of substantive content) and could benefit from splitting Docker setup or script details into separate files. The Resources section provides external links, and Next Steps references another skill, but the inline content is heavy for a SKILL.md overview. | 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.