CtrlK
BlogDocsLog inGet started
Tessl Logo

docusign-automation

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/docusign-automation/SKILL.md

The canonical home for this skill is docusign-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-structured and actionable, with clearly sequenced workflows and verification checkpoints. Its main weaknesses are redundancy (Known Pitfalls repeats per-workflow pitfalls) and a non-informative closing 'When to Use' line, which together depress conciseness.

Suggestions

Remove or fold the 'Known Pitfalls' section into the per-workflow pitfalls to eliminate duplication, or prune it to only pitfalls not already stated.

Replace the filler 'When to Use' line with concrete trigger conditions (e.g. 'Use when the user wants to send, track, void, or add documents to DocuSign envelopes').

Add an explicit error-recovery note for the auth/connection step (e.g. what to do if the OAuth link flow fails) to strengthen feedback loops.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the 'Known Pitfalls' section largely duplicates per-workflow pitfalls (role case-sensitivity, status meanings, GUIDs) and the trailing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') is filler.

3 / 5

Actionability

Concrete tool slugs, explicit parameter names and values (templateRoles, status 'created'/'sent', roleName/name/email), and a quick-reference table give actionable, executable guidance with only minor gaps.

4 / 5

Workflow Clarity

Numbered tool sequences with explicit verification checkpoints ('Confirm connection status shows ACTIVE before running any workflows', 'Verify envelope exists and is in draft state [Prerequisite]') are clear, though explicit validate→fix→retry feedback loops are absent.

4 / 5

Progressive Disclosure

A self-contained SKILL.md with well-organized sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference) and no bundle files; structure is good but the redundant pitfalls/filler sections leave minor organization gaps.

4 / 5

Total

15

/

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.

The description is specific and clearly distinguishable, but it omits an explicit 'when to use' trigger clause, which caps its completeness score. Adding a 'Use when...' sentence referencing natural triggers (sending documents for signature, tracking envelopes, managing DocuSign templates) would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to send documents for e-signature, track DocuSign envelope status, or manage DocuSign templates.'

Drop or relocate the operational aside 'Always search tools first for current schemas.' from the description into the body, since it is guidance rather than a capability statement.

Include a few natural synonyms (e.g. 'e-signature', 'electronic signature') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the DocuSign domain and several concrete capability areas ('templates, envelopes, signatures, document management'), with only minor coverage gaps relative to the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear ('Automate DocuSign tasks... templates, envelopes, signatures, document management') but there is no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'DocuSign', 'envelopes', 'templates', and 'signatures' are natural terms users would say, though 'Rube MCP (Composio)' is technical jargon and a few natural synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

'Automate DocuSign tasks via Rube MCP' carves out a clear, narrowly-scoped niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.