docusign-automation

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

Install with Tessl CLI

npx tessl i github:davepoon/buildwithclaude --skill docusign-automation

What are skills?

2.00x

Quality

51%

Does it follow best practices?

Impact

88%

2.00x

Average score across 3 eval scenarios

Optimize this skill with Tessl

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

SKILL.md

Review

Evals

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 specific tooling) but suffers from lack of explicit trigger guidance and somewhat generic capability listing. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill, and the capabilities listed are categories rather than concrete actions.

Suggestions

Add a 'Use when...' clause with trigger terms like 'DocuSign', 'e-signature', 'send for signing', 'electronic signature', 'contract signing'

Replace category labels with specific actions: 'Create and send envelopes for signature, manage signing templates, track document status, download signed documents'

Include common user phrases like 'get someone to sign', 'send contract for signature', 'check signing status'

Dimension	Reasoning	Score
Specificity	Names the domain (DocuSign) and lists some actions (templates, envelopes, signatures, document management), but these are category labels rather than concrete actions like 'create envelope', 'send for signature', or 'track signing status'.	2 / 3
Completeness	Describes what it does (DocuSign automation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The instruction to 'search tools first' is operational guidance, not selection criteria.	1 / 3
Trigger Term Quality	Includes 'DocuSign', 'templates', 'envelopes', 'signatures' which are relevant keywords, but misses common user phrases like 'e-signature', 'sign document', 'send for signing', 'electronic signature', or 'contract signing'.	2 / 3
Distinctiveness Conflict Risk	DocuSign is a specific product/service with clear branding, and the mention of 'Rube MCP (Composio)' further narrows the scope. Unlikely to conflict with other skills due to the specific platform focus.	3 / 3
	Total	8 / 12 Passed

Implementation

62%

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

This is a solid skill with excellent workflow clarity and good organization. The main weaknesses are the lack of concrete, executable examples (actual MCP tool call JSON) and some redundancy in explaining concepts like envelope status. The skill would benefit from showing actual tool invocation examples rather than just listing parameters.

Suggestions

Add concrete MCP tool call examples with actual JSON payloads for at least one complete workflow (e.g., creating and sending an envelope from template)

Remove duplicate explanations of envelope status meanings - consolidate into the 'Envelope Status Flow' section only

Replace pseudocode patterns in 'Common Patterns' section with actual executable tool call examples

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what 'delivered' vs 'signed' means multiple times across sections). The envelope status flow is repeated in both the workflow section and Known Pitfalls.	2 / 3
Actionability	Provides clear tool sequences and parameter lists, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style notation rather than actual MCP tool call examples with concrete JSON payloads.	2 / 3
Workflow Clarity	Excellent workflow sequencing with clear [Required]/[Optional]/[Prerequisite] markers, explicit tool sequences for each use case, and a clear status flow diagram. Validation steps are implicit but appropriate for API-based workflows.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in a single file. The Quick Reference table is helpful, but detailed workflows could be split into separate files. The external toolkit docs link is good but underutilized.	2 / 3
	Total	9 / 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

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