Name: docusign
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

docusign

DocuSign integration. Manage data, records, and automate workflows. Use when the user wants to interact with DocuSign data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/docusign/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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 concrete CLI commands and a clear state-driven connection workflow. Tightening the introductory concept explanations and moving the large actions table to a reference file would improve it.

Suggestions

Trim the opening paragraph and DocuSign Overview glossary that restate what DocuSign is; assume Claude's knowledge.

Consider moving the Popular actions table to a references/actions.md file and linking to it, keeping only the most common actions inline.

Make step numbering consistent (e.g., explicitly number "Step 2" and the connection sub-steps) so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but the opening platform description and the DocuSign Overview glossary explain concepts Claude already knows.	3 / 5
Actionability	Fully executable, copy-paste ready commands cover install, login, connection, action listing/running, and proxy requests, plus a concrete actions table and flag table.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though section numbering is slightly inconsistent.	4 / 5
Progressive Disclosure	Well-organized with clear headers and no nested references, but the large inline Popular actions table (~20 rows) is reference material that, in a skill this size, could live in a separate file.	4 / 5
	Total	16 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 has an explicit Use-when trigger and a distinctive brand keyword, but its action language is generic rather than naming concrete DocuSign capabilities. Adding specific actions (send/sign envelopes, list templates) and natural trigger terms would raise it.

Suggestions

Replace generic actions with concrete DocuSign actions, e.g. "send and sign envelopes, list and create templates, download documents".

Add natural trigger terms users would say, such as "signatures", "signing", "contracts", or "agreements".

Make the Use-when clause more specific, e.g. "Use when the user wants to send or sign documents, manage envelopes, or work with DocuSign templates."

Dimension	Reasoning	Score
Specificity	It names the DocuSign domain but the listed actions ("Manage data, records", "automate workflows") are generic rather than concrete DocuSign-specific actions like sending envelopes or signing.	2 / 5
Completeness	Both a "what" (DocuSign integration managing data, records, workflows) and an explicit "Use when the user wants to interact with DocuSign data" trigger are present, though neither is fully concrete.	4 / 5
Trigger Term Quality	It covers the brand keyword "DocuSign" but misses common natural synonyms and variations a user would say (envelopes, signatures, signing, contracts, agreements).	3 / 5
Distinctiveness Conflict Risk	The "DocuSign" brand trigger is distinctive with minimal conflict risk, but the generic action language slightly dilutes the niche.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/docusign/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.