docusign-automation

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

2.00x

Quality

76%

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

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

A strong instruction-only skill body: concrete tool sequences, exact parameters, and honest pitfalls make it immediately actionable. Minor room to improve by de-duplicating pitfall content and adding explicit error-recovery feedback loops around envelope creation/sending.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (e.g., 'Template IDs are GUIDs', status semantics, exact parameter names), but the 'Known Pitfalls' section duplicates per-workflow pitfalls (role case-sensitivity and 'delivered' vs 'signed' each appear twice), which could be trimmed.	4 / 5
Actionability	Every workflow gives exact tool slugs, required parameters, numbered sequences, and a concrete templateRoles JSON example, plus a quick-reference table — fully actionable guidance covering all common cases.	5 / 5
Workflow Clarity	Sequences are clearly numbered and tagged [Required]/[Optional]/[Prerequisite], with setup validation ('Confirm connection status shows ACTIVE before running any workflows'). Not 5: no explicit feedback loops, e.g. error recovery when envelope creation fails on a missing role, or post-send status confirmation.	4 / 5
Progressive Disclosure	Well-organized single file with clear section headers, per-workflow structure, and a quick-reference table; no bundle files exist to evaluate. Not 5: at ~205 lines, the detailed per-workflow pitfalls and role-mapping material could be split into a reference file to keep the overview leaner.	4 / 5
	Total	17 / 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.

A fairly strong description: specific domain, concrete capability nouns, and a unique niche. Its main weakness is the missing 'when to use' guidance, which both caps completeness and weakens trigger discoverability for phrasings like 'e-signature' or 'send for signature'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions DocuSign, wants to send documents for e-signature, or asks about envelopes, signing templates, or signature status.'

Include natural synonym phrasings users actually say — 'e-signature', 'electronic signature', 'sign documents', 'send for signature' — alongside the existing tool-level nouns.

Replace the vague 'document management' with the concrete actions behind it (e.g., 'add templates to envelopes', 'void envelopes') to lift specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('templates, envelopes, signatures') tied to a named domain, but the only action verb is the generic 'Automate' and 'document management' is vague, so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	The 'what' is clear (automate DocuSign templates, envelopes, signatures), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'DocuSign', 'templates', 'envelopes', and 'signatures' are natural terms users would say, but common variations like 'e-signature', 'sign documents', or 'send for signature' are missing, so keyword coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	'DocuSign via Rube MCP (Composio)' is a clear niche with distinct triggers; it is unlikely to fire for unrelated skills and conflicts with virtually nothing.	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: b90e2de

Reviewed: 3 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.