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".
64
77%
Does it follow best practices?
Impact
—
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-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 ('configuring dev environment', 'establishing rapid iteration patterns') rather than listing concrete specific actions the skill performs. Adding more specific actions would strengthen it further.
Suggestions
Replace generic phrases like 'establishing rapid iteration patterns' with concrete actions such as 'configure database, install dependencies, run test suites, set up hot-reload'
| 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'. Very 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, actionable skill with complete executable code examples covering Docker setup, SDK client configuration, verification, and cleanup. Its main weaknesses are the lack of explicit validation checkpoints between steps (especially after Docker startup) and the monolithic structure that could benefit from splitting into referenced files. The content is mostly efficient but has room for tightening.
Suggestions
Add an explicit validation checkpoint after Docker setup (Step 4) instructing to wait for healthy containers and run the verify script before proceeding, e.g., 'docker compose up -d && sleep 10 && npm run dev:verify'
Add a dry-run or confirmation prompt to the cleanup script since it performs destructive delete operations on documents
Consider splitting the docker-compose.local.yml and longer scripts into bundle files referenced from the SKILL.md to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements—the project structure tree is somewhat verbose, and the env file examples repeat similar patterns. The client wrapper code and cleanup script are useful but could be tightened. Some comments are redundant (e.g., '# Configured SDK client'). | 2 / 3 |
Actionability | Fully executable TypeScript code, complete docker-compose configuration, concrete package.json scripts, and specific environment variable examples. Everything is copy-paste ready with real SDK method calls and proper error handling patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there's no explicit validation checkpoint after Docker setup (e.g., verifying the database is ready before proceeding). The cleanup script handles destructive operations (deletion) but lacks a confirmation step or dry-run mode. The verify script exists but isn't explicitly called out as a mandatory checkpoint between steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and an error handling table, but it's a long monolithic file (~180 lines of content) that could benefit from splitting Docker config and scripts into separate referenced files. The 'Next Steps' reference to 'documenso-sdk-patterns' is good but there are no bundle files to support progressive disclosure. | 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
8a9cd04
- 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.