docusign-automation

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

2.00x

Quality

45%

Does it follow best practices?

Impact

88%

2.00x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/docusign-automation/SKILL.md

Quality

Discovery

40%

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 identifies a clear niche (DocuSign automation via Composio) which makes it distinctive, but it lacks an explicit 'Use when...' clause and lists capabilities at a category level rather than as specific concrete actions. The implementation instruction ('Always search tools first') takes up space that could be better used for trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about DocuSign, e-signatures, sending documents for signing, or managing signature workflows.'

Replace the generic category labels with specific concrete actions, e.g., 'Create and send envelopes, manage templates, track signature status, download signed documents.'

Move the implementation detail ('Always search tools first for current schemas') into the skill body rather than the description, and use that space for natural trigger terms like 'e-signature', 'sign documents', 'electronic signature'.

Dimension	Reasoning	Score
Specificity	Names the domain (DocuSign) and lists some actions (templates, envelopes, signatures, document management), but these are more like category labels than specific concrete actions. It doesn't describe what exactly is done with templates or envelopes (e.g., 'create envelopes', 'send for signature', 'list templates').	2 / 3
Completeness	Describes what it does (automate DocuSign tasks) but has no explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail, not a trigger condition. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also somewhat thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'DocuSign', 'templates', 'envelopes', 'signatures', and 'document management', which users might naturally say. However, it misses common variations like 'e-signature', 'sign documents', 'send for signing', 'Composio', or 'electronic signature'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'DocuSign' and 'Rube MCP (Composio)' creates a very clear niche. It's unlikely to conflict with other skills since DocuSign is a specific platform, and the tooling context (Composio) further narrows it.	3 / 3
	Total	8 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid structural overview of DocuSign automation workflows with clear tool sequences and useful parameter documentation. Its main weaknesses are redundancy (pitfalls repeated in multiple places), lack of executable call examples (pseudocode rather than actual MCP invocation syntax), and missing validation/error-recovery steps for irreversible operations like sending envelopes.

Suggestions

Consolidate the repeated pitfalls into the single 'Known Pitfalls' section and remove duplicates from individual workflows to reduce token usage by ~30%.

Add at least one concrete, executable MCP call example showing the actual invocation syntax (e.g., a complete RUBE_SEARCH_TOOLS call followed by DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE with real parameter structure).

Add explicit validation checkpoints to workflows involving irreversible actions—e.g., after creating an envelope, verify recipient assignments before calling SEND_ENVELOPE, with error recovery guidance if validation fails.

Consider splitting detailed workflow descriptions into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and links to details.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but has significant redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section (e.g., role case-sensitivity, envelope status meanings, GUID format). The 'Common Patterns' section also partially duplicates workflow steps. Some trimming would improve token efficiency.	2 / 3
Actionability	Tool sequences are clearly named and parameters are specified, which is helpful. However, there are no executable code examples or actual MCP call syntax—just tool names and parameter lists. The 'Common Patterns' section uses pseudocode-style numbered lists rather than concrete, copy-paste-ready invocations. Claude would need to infer exact call formats.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), and the envelope status flow diagram is useful. However, there are no explicit validation checkpoints or error recovery loops—e.g., no 'if creation fails, check X and retry' guidance. For operations like sending envelopes (which are irreversible per the skill's own notes), this is a notable gap.	2 / 3
Progressive Disclosure	The content is well-organized with clear headers and a quick reference table, but it's a monolithic ~150-line document with no bundle files to offload detail into. The repeated pitfalls sections and detailed workflow descriptions could be split into separate reference files. The single external link to Composio docs is appropriate but insufficient for progressive disclosure.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: d065ead

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