Automate Big Data Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/big-data-cloud-automation/SKILL.mdQuality
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 effectively guide skill selection. It names specific tools (Rube MCP, Composio) but fails to explain what concrete actions are possible or when the skill should be triggered. The procedural note about searching tools first is implementation detail rather than useful selection criteria.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user mentions Big Data Cloud, Composio integrations, or needs to automate cloud data pipelines'
Replace 'tasks' with specific concrete actions like 'create data pipelines, manage cloud storage, schedule batch jobs, monitor data workflows'
Include natural language variations users might say, such as 'data automation', 'cloud ETL', 'batch processing', or specific Composio operation names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Big Data Cloud tasks' without specifying what concrete actions can be performed. 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('tasks') and there is no 'Use when...' clause or explicit trigger guidance. The description fails to answer when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Big Data Cloud', 'Rube MCP', 'Composio') but these are technical/product-specific terms. Missing natural user language variations for what tasks users might request. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Rube MCP, Composio, Big Data Cloud) provide some distinctiveness, but 'tasks' is so generic it could overlap with any automation skill. The niche is unclear. | 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 Big Data Cloud automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content is appropriately concise. The main weakness is that tool call examples use placeholder arguments rather than concrete, copy-paste ready examples with realistic values.
Suggestions
Add a concrete end-to-end example with realistic arguments (e.g., a specific Big Data Cloud operation with actual field values) to improve actionability
Include an example of what a successful RUBE_SEARCH_TOOLS response looks like so Claude knows what to expect and how to parse it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Big Data Cloud is or how MCP works. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but the examples are pseudocode-like structures rather than fully executable code. The arguments sections use placeholders like 'schema-compliant args from search results' instead of concrete examples. | 2 / 3 |
Workflow Clarity | Clear 4-step setup sequence with explicit validation checkpoint (confirm ACTIVE status before proceeding). The 3-step core workflow pattern is well-sequenced with clear dependencies between steps. | 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 provides efficient navigation. | 3 / 3 |
Total | 11 / 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 | |
2790447
Table of Contents
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.