docusign-automation
Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.
65
51%
Does it follow best practices?
Impact
88%
2.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/docusign-automation/SKILL.mdQuality
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 as nouns rather than concrete actions. The instruction about searching tools first is an implementation detail that doesn't help with skill selection.
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 noun-based capability listing with concrete action verbs, 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') out of the description or reframe it, as it doesn't help Claude decide when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DocuSign) and lists some actions (templates, envelopes, signatures, document management), but these are more like category nouns than concrete actions. It doesn't specify verbs like 'create envelopes', 'send for signature', 'list templates', etc. | 2 / 3 |
Completeness | It describes what it does (automate DocuSign tasks) but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail, not a trigger condition. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'DocuSign', 'templates', 'envelopes', 'signatures', and 'document management', which users might naturally say. However, it's missing common variations like 'e-signature', 'sign documents', 'send for signing', 'Composio', or 'electronic signature'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to DocuSign via Rube MCP (Composio), which is a very specific niche. It's unlikely to conflict with other skills given the explicit mention of DocuSign and the specific integration platform. | 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 well-structured skill with clear workflow sequences and good awareness of pitfalls, but it suffers from significant internal redundancy (pitfalls repeated across sections) and lacks truly executable examples (no complete MCP tool call payloads). The content would benefit from deduplication and adding concrete, copy-paste-ready tool invocation examples.
Suggestions
Deduplicate pitfalls: consolidate all pitfalls into the 'Known Pitfalls' section and reference it from workflows instead of repeating the same warnings (role case-sensitivity, GUID format, status meanings) in every workflow section.
Add at least one complete, executable MCP tool call example with actual JSON parameters for a common workflow like creating and sending an envelope from a template.
Consider extracting the detailed workflow sections into a separate reference file and keeping SKILL.md as a concise overview with the quick reference table and setup instructions.
| 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, GUID format, envelope status meanings are stated 3+ times). The 'Common Patterns' section also restates workflow steps already covered. Could be tightened by ~30%. | 2 / 3 |
Actionability | Tool sequences are clearly named and parameters are specified, but there are no actual executable code/command examples — the patterns section uses pseudocode-like numbered steps rather than real MCP tool calls with concrete JSON payloads. The role mapping example shows a JSON fragment but not a complete tool invocation. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), explicit ordering, and status preconditions (e.g., 'envelope must be in created status'). The envelope status flow diagram and validation checkpoints (verify connection is ACTIVE, check envelope status before modifications) provide good guardrails. | 3 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files to reference. While it has good internal section structure, the document is quite long (~150+ lines of content) and the detailed pitfalls, common patterns, and quick reference could benefit from being split out. The external link to Composio docs is helpful but there's no layered reference structure. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
74c7031
- Reviewed
Table of Contents
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.