CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

boloforms-automation

Automate Boloforms 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/boloforms-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is concise and actionable with well-structured tool-call examples and a clear sequence, but batch execution lacks an explicit result-verification feedback loop and the single-file structure has minor organization room.

Suggestions

Add an explicit verify/retry step after RUBE_MULTI_EXECUTE_TOOL (check response status/errors, re-run failed tools) to satisfy the batch-operation feedback-loop requirement.

Consolidate the repeated 'search first' guidance into a single canonical statement to remove redundancy.

Consider extracting the Known Pitfalls or Quick Reference into a one-level reference file to improve progressive disclosure now that the file exceeds 50 lines.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented with code blocks, with only minor redundancy (e.g. 'search first' restated across Prerequisites, Tool Discovery, and Pitfalls), matching the efficient-with-minor-trim anchor.

4 / 5

Actionability

Concrete tool-invocation code blocks with real parameter shapes are provided; placeholders appear only for inherently dynamic values (session_id, tool_slug), giving mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

Steps are clearly sequenced with a pre-execution checkpoint (confirm ACTIVE), but RUBE_MULTI_EXECUTE_TOOL is a batch operation lacking a validate->fix->retry feedback loop on results, triggering the batch-ops cap at 3.

3 / 5

Progressive Disclosure

A single self-contained file is well organized with clear section headers and a Quick Reference table; at over 50 lines the simple-skill 5 exception does not apply, and a one-level reference could still help, so it sits at good-structure-with-minor-gaps.

4 / 5

Total

15

/

20

Passed

Description

57%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 clearly names its niche and states one concrete action, but lacks an explicit 'when to use' trigger clause and relies on mostly technical jargon, capping completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when automating Boloforms workflows, managing Boloforms tasks, or integrating Boloforms with other tools.'

List 1-2 more concrete actions beyond 'search tools first' (e.g. 'discover tools, manage connections, and execute Boloforms operations') to raise specificity.

Replace some jargon ('Rube MCP', 'Composio') with user-facing synonyms or include Boloforms-related keywords users would naturally say.

DimensionReasoningScore

Specificity

Names the domain ('Boloforms tasks') and one concrete action ('search tools first for current schemas'), but does not enumerate a comprehensive set of actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

The 'what' is clear (automate Boloforms via Rube MCP), but there is no 'Use when...' or equivalent explicit trigger guidance, so the missing-trigger cap at 3 applies.

3 / 5

Trigger Term Quality

'Boloforms tasks' is a natural phrase a user would say, but the rest ('Rube MCP', 'Composio') is technical jargon and common synonyms/variations are missing, falling at the lower edge of the relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

'Boloforms' is a narrow, specific toolkit niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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/boloforms-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.