bidsketch-automation

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

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/bidsketch-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be useful for skill selection. It names the target platform (Bidsketch) but fails to describe what specific actions can be performed or when Claude should select this skill. The procedural note about searching tools first is implementation detail that doesn't help with skill selection.

Suggestions

Add specific capabilities like 'Create proposals, manage clients, track proposal status, send documents for signature'

Add a 'Use when...' clause with trigger terms like 'proposal', 'quote', 'estimate', 'Bidsketch', 'sales document', 'client proposal'

Remove implementation details ('Always search tools first') and focus on user-facing functionality

Dimension	Reasoning	Score
Specificity	The description says 'Automate Bidsketch tasks' which is extremely vague - it doesn't specify what tasks can be automated (creating proposals, managing clients, sending documents, etc.). 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely weak ('automate tasks' is not specific), and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer either question adequately.	1 / 3
Trigger Term Quality	Includes 'Bidsketch' which is a specific product name users might mention, but lacks natural variations like 'proposals', 'quotes', 'estimates', 'sales documents' that users would actually say when needing this functionality.	2 / 3
Distinctiveness Conflict Risk	'Bidsketch' is a specific product which provides some distinctiveness, but 'automate tasks via Rube MCP (Composio)' could apply to many integration skills, creating potential overlap with other Composio-based automations.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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 that efficiently guides Claude through Bidsketch automation via Rube MCP. The workflow is clear with proper validation steps, and the content is appropriately concise. The main weakness is that the tool call examples use placeholder syntax rather than showing concrete, realistic parameter values that would make the guidance more immediately actionable.

Suggestions

Replace pseudocode tool calls with concrete examples showing realistic Bidsketch operations (e.g., creating a proposal with actual field values)

Add a brief example showing a complete end-to-end workflow with actual tool slugs and arguments that might be returned from RUBE_SEARCH_TOOLS

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Bidsketch or MCP are. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudocode-style notation rather than fully executable code. The arguments are placeholders rather than real examples with actual values.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint for connection status and explicit 'Known Pitfalls' section for error prevention.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 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: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 2 months 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.