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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, code-heavy body with concrete executable examples and a clear step sequence, undermined by a few incomplete/buggy snippets and a bundle reference file that is neither linked nor cleanly separated from the inline content.

Suggestions

Link to `references/implementation-guide.md` from the body (e.g., a "## Implementation details" pointer) so the bundle reference is actually surfaced, and move the full docker-compose / script listings there to reduce inline duplication.

Add the missing `scripts/create-test-doc.ts` source (referenced in package.json's `dev:test-doc`) or remove that script entry so the package.json examples are self-consistent.

Add a validation/confirmation gate before the destructive cleanup in Step 6 (e.g., list-then-confirm or a `--dry-run` flag) and fix the verify script's always-true `documents.length >= 0` check.

Dimension	Reasoning	Score
Conciseness	The body is code- and config-heavy with minimal prose, assumes Claude's competence, and avoids explaining concepts Claude already knows — every section earns its place.	3 / 3
Actionability	Most snippets are executable TypeScript/YAML/bash, but there are real gaps: package.json references a `create-test-doc.ts` script whose source is never shown, the verify script's `documents.length >= 0` check is always true, and Step 4 mixes a bash and yaml fence incorrectly.	2 / 3
Workflow Clarity	Seven steps are clearly sequenced with a verification checkpoint and an error-handling table, but the destructive batch cleanup (Step 6) has no validation/confirm gate before deletion, capping this dimension at 2 per the rubric.	2 / 3
Progressive Disclosure	Sections are organized, but the provided bundle file `references/implementation-guide.md` is never referenced or signaled from the body, and substantial inline detail (full docker-compose, multiple full scripts) that could live in the reference instead duplicates it.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that concisely states concrete capabilities, gives explicit "Use when" trigger guidance, and lists natural trigger phrases scoped to a clear Documenso-local-dev niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Set up local development environment and testing workflow", "configuring dev environment", "setting up test workflows", "establishing rapid iteration patterns" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (set up local dev environment and testing workflow) and when (a clear "Use when..." clause plus trigger phrases), matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ("documenso local dev", "documenso development", "test documenso locally", "documenso dev environment") with good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to Documenso local development with distinctive, product-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/documenso-pack/skills/documenso-local-dev-loop/SKILL.md
Commit: 399d94c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.