documenso-install-auth

Install and configure Documenso SDK/API authentication. Use when setting up a new Documenso integration, configuring API keys, or initializing Documenso in your project. Trigger with phrases like "install documenso", "setup documenso", "documenso auth", "configure documenso API key".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The body is highly actionable with a clear, validated install-and-auth workflow and strong error/security guidance. Its main weaknesses are redundancy (serverURL shown twice, a legacy v1 path) and an unreferenced bundle file that duplicates the inline content.

Suggestions

Consolidate the `serverURL` self-hosted override to one place — it currently appears as a comment in Step 4 and again as its own section — to remove redundancy and tighten the body.

Either link `references/implementation-guide.md` from the body or remove it: the bundle file currently duplicates the SKILL content and is never referenced, which weakens progressive disclosure.

Consider moving the v1 legacy REST path into the reference file since v2 is recommended for new work, reducing token cost while keeping the primary guidance inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-forward, but the `serverURL` override appears both as a comment in Step 4 and again as its own section, and the v1 legacy REST path adds length for a discouraged path — it could be tightened. Not 3 because of this redundancy; not 1 because it avoids explaining basics Claude already knows.	2 / 3
Actionability	Provides executable `npm install`/`pip install` commands, `.env` setup, TypeScript and Python client init, and a runnable `verify-connection.ts` invoked with `npx tsx` — copy-paste ready, matching the score-3 anchor.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with an explicit "Verify the Connection" checkpoint, a supporting error-handling table, and a security checklist, matching the score-3 anchor; not 2 because validation is explicit rather than merely implied.	3 / 3
Progressive Disclosure	Sections are well-organized, but `references/implementation-guide.md` exists and is never linked from the body and largely duplicates the SKILL content — references present but not signaled, matching the score-2 anchor; not 3 because the bundle file is not woven in as a one-level-deep reference.	2 / 3
	Total	10 / 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 strong, third-person description that states concrete capabilities and provides explicit 'Use when' trigger guidance with natural phrasing. It is distinctive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Quotes "Install and configure Documenso SDK/API authentication" plus "setting up a new Documenso integration, configuring API keys, or initializing Documenso" — it enumerates several distinct concrete actions (install, configure API keys, initialize), matching the score-3 anchor rather than merely naming the domain.	3 / 3
Completeness	Explicitly answers both: "Install and configure Documenso SDK/API authentication" (what) and "Use when setting up a new Documenso integration, configuring API keys, or initializing Documenso in your project" (when), with explicit trigger guidance, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Lists natural phrases a user would actually say — "install documenso", "setup documenso", "documenso auth", "configure documenso API key" — covering common variations, matching the score-3 anchor rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Documenso-specific niche with brand-named triggers, making it unlikely to fire for unrelated skills, matching the score-3 anchor; not score 2 because the scope is narrowly bounded to one product's auth setup.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/documenso-pack/skills/documenso-install-auth/SKILL.md
Commit: 4c47e33

Reviewed: about 17 hours 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.