CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

boldsign-automation

Automate Boldsign tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

69%

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 ./composio-skills/boldsign-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A compact, well-structured automation skill with concrete tool-call examples and good navigation, but its multi-execute workflow lacks explicit validation/verification checkpoints for batch or destructive operations, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint in the Core Workflow Pattern (e.g., inspect RUBE_MULTI_EXECUTE_TOOL response for errors before proceeding, and retry failed tools).

Clarify how to handle pagination and partial failures when executing multiple tools in RUBE_MULTI_EXECUTE_TOOL.

Replace placeholder session IDs with guidance on generating vs reusing them to make the examples more copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows; it uses compact code blocks and a table, though a few pitfalls and the setup prose repeat information already conveyed elsewhere.

4 / 5

Actionability

Provides concrete, near-executable tool-call blocks (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with parameter shapes and a quick-reference table; minor gaps include placeholder session IDs and unspecified exact argument fields.

4 / 5

Workflow Clarity

The Core Workflow Pattern lists three sequenced steps and the Known Pitfalls mention checking connection status, but the destructive/batch nature of execution (RUBE_MULTI_EXECUTE_TOOL) lacks explicit validate-then-retry checkpoints, capping this at 3.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), and this under-50-line skill is well-organized into clear sections with a quick-reference table; per the simple-skill exception, this earns a 5.

5 / 5

Total

16

/

20

Passed

Description

53%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 to a named product and uses third person, but it is generic about which Boldsign operations are supported and omits any 'Use when...' trigger guidance, capping completeness. Adding concrete actions and trigger phrases would lift it.

Suggestions

Enumerate concrete Boldsign actions (e.g., send documents for signature, track envelope status, download signed files).

Add an explicit trigger clause such as 'Use when the user asks to send or track Boldsign e-signature envelopes.'

Include natural user synonyms like 'e-signature', 'signing', or 'envelope' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Boldsign tasks) and one concrete action ('search tools first'), but the remainder is the generic verb 'Automate...tasks' without enumerating what Boldsign operations are supported.

3 / 5

Completeness

There is a clear 'what' (automate Boldsign tasks via Rube MCP) but no explicit 'when/Use when...' clause; the cap for missing trigger guidance is 3.

3 / 5

Trigger Term Quality

Includes the natural term 'Boldsign' and 'tasks', but lacks common user phrasings or synonyms (e.g., e-signature, signing documents, sending for signature) that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

'Boldsign' is a specific named product, so it is largely distinct from other skills; only minor overlap risk with general Composio/MCP automation skills.

4 / 5

Total

13

/

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.

Validation — 15 / 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

ComposioHQ/awesome-claude-skills

Path

composio-skills/boldsign-automation/SKILL.md

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.