CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with complete executable examples and a clear step sequence, but it is weighed down by duplication of a bundled reference that is never linked, and its destructive cleanup lacks an explicit validation checkpoint.

Suggestions

Replace the duplicated inline project structure, client wrapper, and scripts in SKILL.md with a concise overview that links to references/implementation-guide.md for full details.

Add an explicit validation/dry-run step before the Step 6 cleanup deletes documents (e.g., list-and-confirm before deleteV0) to close the destructive-operation gap.

Tighten the docker-compose block or move it into the reference so the body stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

The body is mostly efficient with code that earns its place and little concept explanation, but it carries full inline implementations (client wrapper, docker-compose, verify/cleanup scripts, package.json) that largely duplicate the bundled reference, so it could be tightened.

2 / 3

Actionability

It provides fully executable TypeScript, a complete docker-compose.local.yml, env files, verify/cleanup scripts, and package.json entries that are copy-paste ready.

3 / 3

Workflow Clarity

Steps 1-7 are clearly sequenced and a verify checkpoint exists (Step 5), but the destructive batch cleanup (Step 6) has no dry-run/confirm validation gate before deleting documents, which caps clarity per the rubric's destructive-operation rule.

2 / 3

Progressive Disclosure

A references/implementation-guide.md bundle exists, but the SKILL.md body never links to or signals it and instead duplicates much of the same content inline, so the reference is present but not clearly navigated.

2 / 3

Total

9

/

12

Passed

Description

90%

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

The description is well-structured with clear 'what' and 'when' guidance and natural trigger phrases tied to a specific product niche. Its only weakness is that the stated actions are somewhat high-level rather than enumerating multiple concrete capabilities.

Suggestions

Replace the generic 'configuring dev environment, setting up test workflows, or establishing rapid iteration patterns' with specific concrete actions such as 'generate test documents, run connection checks, self-host Documenso via Docker, and clean up test data'.

DimensionReasoningScore

Specificity

The description names the domain and some actions ('Set up local development environment and testing workflow', 'configuring dev environment', 'setting up test workflows') but stays high-level rather than listing multiple concrete, distinct actions like the score-3 anchor.

2 / 3

Completeness

It answers both 'what' ('Set up local development environment and testing workflow for Documenso') and 'when' via an explicit 'Use when...' clause plus a 'Trigger with phrases like...' trigger list.

3 / 3

Trigger Term Quality

Explicit natural phrases are provided ('documenso local dev', 'documenso development', 'test documenso locally', 'documenso dev environment') giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It targets a clear Documenso-specific niche with distinct, product-scoped triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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