docusign-automation

Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.

2.00x

Quality

72%

Does it follow best practices?

Impact

88%

2.00x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/docusign-automation/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 tool slugs, exact parameters, and copy-paste examples, and workflows are clearly sequenced with status-check prerequisites. The main weakness is redundancy between per-workflow pitfalls, the Known Pitfalls section, and the Quick Reference table, which slightly hurts conciseness.

Suggestions

Consolidate the redundant 'Known Pitfalls' section and per-workflow 'Pitfalls' blocks to remove repetition and improve token efficiency.

Add an explicit validate-then-confirm checkpoint for the destructive void operation in the 'Manage Envelope Lifecycle' workflow (e.g. confirm envelope status and user intent before voiding).

Consider moving the Quick Reference table and detailed pitfall catalog into a reference file to sharpen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the 'Known Pitfalls' section and 'Quick Reference' table largely restate pitfalls and tool slugs already covered per-workflow, so it is mostly efficient with notable redundancy that could be tightened.	3 / 5
Actionability	Provides exact tool slugs, precise parameter names (templateId, templateRoles, status, envelopeId), a copy-paste-ready templateRoles JSON object, and a status flow diagram, giving fully executable guidance that covers the common cases.	5 / 5
Workflow Clarity	Each workflow has a numbered tool sequence with [Required]/[Optional]/[Prerequisite] markers and status-check prerequisites (e.g. confirm ACTIVE connection, verify draft state before adding templates); the destructive void operation lacks an explicit validate-before-void checkpoint, a minor validation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with no nested references and no bundle files; minor organization gaps from the redundant summary sections keep it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

70%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 is specific and distinctive, clearly scoping the DocuSign domain with concrete capability areas and natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' usage trigger, which caps completeness at 3.

Suggestions

Add an explicit usage trigger clause, e.g. 'Use when the user needs to send or track DocuSign envelopes, manage templates, or handle e-signatures.'

Include common synonyms/extensions (e-signature, signing, .docuSign) to broaden trigger-term coverage toward a 5.

Dimension	Reasoning	Score
Specificity	Names the DocuSign domain and lists several concrete action areas ('templates, envelopes, signatures, document management') with only minor coverage gaps, matching the 'lists several specific actions' anchor.	4 / 5
Completeness	The 'what' is clear (automate DocuSign tasks) but there is no 'Use when...' trigger clause — the trailing 'Always search tools first' is operational guidance, not a usage trigger, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains natural user-facing terms ('DocuSign', 'templates', 'envelopes', 'signatures') but lacks synonyms/extensions like 'e-signature' or 'signing', fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	'DocuSign' is a clear niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/docusign-automation/SKILL.md
Commit: a9fa86d

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