CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-multi-env-setup

Configure Documenso across multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows. Trigger with phrases like "documenso environments", "documenso staging", "documenso dev setup", "multi-environment documenso".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 code-rich, actionable skill body with clear sections, but it suffers from redundancy between the architecture diagram and config files, missing validation feedback loops for destructive operations, and an orphaned reference file that is never signaled.

Suggestions

Remove the redundancy between the ASCII architecture diagram and Step 1's .env files — keep one canonical source for URLs/keys/webhooks and reference it.

Add explicit validate→fix→retry checkpoints to the promotion and batch/destructive workflows (e.g., verify keys and dry-run in staging before promoting to production).

Link to references/implementation-guide.md from the body (e.g., a "## Implementation details" section) and move the heavy inline code into it so SKILL.md stays an overview.

DimensionReasoningScore

Conciseness

The body is mostly lean code and tables, but the ASCII architecture diagram restates the same URLs, keys, and webhook endpoints already given in Step 1's .env files and the checklist, introducing redundancy that could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript (client factory, environment guards, mock client, template config) and concrete bash .env files, with no pseudocode gaps.

3 / 3

Workflow Clarity

Five clearly sequenced steps plus a checklist and error-handling table, but destructive/batch operations (deleteAllDrafts, sendBulkContracts, environment promotion) lack explicit validate→fix→retry feedback loops, capping the score per the rubric.

2 / 3

Progressive Disclosure

The body is well-sectioned, but a 429-line references/implementation-guide.md exists that duplicates and expands the body content and is never linked from SKILL.md, leaving an orphaned reference and inline content that could be split out.

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-constructed description that clearly states capability, use-when guidance, and natural trigger phrases in third-person voice, with a distinct Documenso niche. It fully satisfies all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in the domain — "Configure Documenso across multiple environments", "setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows" — rather than vague abstractions, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("Configure Documenso across multiple environments (dev, staging, production)") and when ("Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows") with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say — "documenso environments", "documenso staging", "documenso dev setup", "multi-environment documenso" — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

A clear Documenso-specific multi-environment niche with distinct, product-prefixed triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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