docusign-automation

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

2.00x

Quality

51%

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 ./.trae/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 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 inclusion of an implementation instruction ('Always search tools first') takes up space that could be better used for trigger terms or usage 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 category labels with specific concrete actions, e.g., 'Create and send envelopes, manage signing 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', 'send for signing'.

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 weak, warranting a score of 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 product/service.	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 that clearly documents DocuSign workflow sequences with good validation checkpoints and status-awareness. Its main weaknesses are repetition of pitfalls across sections (hurting conciseness) and lack of executable tool call examples with actual parameter payloads (limiting actionability). The workflow clarity is strong with explicit prerequisite checks and status flow documentation.

Suggestions

Consolidate repeated pitfalls (case-sensitive roles, GUID format, envelope statuses) into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections to reduce token usage by ~25%.

Add at least one complete, copy-paste-ready tool invocation example showing the exact JSON parameters for DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE, rather than just listing parameter names.

Consider moving the 'Known Pitfalls' and 'Common Patterns' sections into a separate reference file to keep the main SKILL.md focused on the core workflow sequences.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but contains significant repetition—pitfalls about case-sensitive role names, GUID formats, and envelope statuses are repeated across individual workflow sections AND the 'Known Pitfalls' summary section. The 'Common Patterns' section also partially duplicates workflow steps. Could be tightened by ~30%.	2 / 3
Actionability	Tool sequences and parameter names are clearly specified, which is good. However, there are no executable code examples or copy-paste-ready tool invocations with actual parameter schemas/JSON payloads. The template role mapping example uses a JSON snippet but it's illustrative rather than a complete tool call. Claude would need to search tools anyway to get exact schemas.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps, prerequisite/required/optional annotations, and explicit status checks before proceeding (e.g., verify envelope is in draft before adding templates, confirm connection is ACTIVE before running workflows). The envelope status flow diagram and validation checkpoints are well-defined.	3 / 3
Progressive Disclosure	The content is entirely contained in one file with no references to supplementary documents, which is acceptable for a skill of this scope. However, at ~150+ lines with repeated pitfalls sections, some content (like the detailed Known Pitfalls or Common Patterns) could be split out. The quick reference table at the end is a nice touch but the overall organization could benefit from clearer separation.	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

Repository: Lingjie-chen/MT5
Commit: 3069d33

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