CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apaleo-automation

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

50

Quality

63%

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

Quality

Content

61%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 well-structured and provides concrete, mostly-executable MCP call patterns with a sensible workflow and connection validation. Its main weaknesses are redundant 'search-first' messaging and a missing result-verification feedback loop around the batch execute step.

Suggestions

State 'search tools first' once in Tool Discovery and reference it elsewhere instead of repeating the full directive in Prerequisites and Known Pitfalls.

Add a post-execution verification step to the Core Workflow (e.g., check RUBE_MULTI_EXECUTE_TOOL response status/errors and retry on failure) to close the batch-operation feedback loop.

Merge the standalone 'Tool Discovery' section into 'Step 1: Discover Available Tools' to remove the near-duplicate content.

DimensionReasoningScore

Conciseness

The body is mostly lean but repeats 'search tools first' across the description, Prerequisites, Tool Discovery, and Known Pitfalls, and the 'Core Workflow Pattern' Step 1 duplicates the earlier 'Tool Discovery' section, so it could be tightened.

3 / 5

Actionability

Concrete MCP calls with real field names (RUBE_SEARCH_TOOLS with queries/session, RUBE_MANAGE_CONNECTIONS with toolkits, RUBE_MULTI_EXECUTE_TOOL with tool_slug/arguments) plus a mapping table give mostly executable guidance, though execute-step values are placeholders (TOOL_SLUG_FROM_SEARCH, your_session_id).

4 / 5

Workflow Clarity

A clear sequence exists with an ACTIVE-status checkpoint before execution, but the batch RUBE_MULTI_EXECUTE_TOOL step has no explicit result-verification or error-retry feedback loop, which caps batch-operation workflow clarity at 3 per the guidelines.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections in a single appropriately-sized file for this integration skill, with a one-level external docs link; no nested references. It exceeds the 50-line simple-skill threshold and has minor inline redundancy, so it is good rather than exemplary.

4 / 5

Total

14

/

20

Passed

Description

48%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 names a specific, distinct niche (Apaleo via Rube MCP) but is generic about capabilities and omits explicit 'use when' trigger guidance. It reads more as a setup directive than a trigger-rich capability statement.

Suggestions

Add a 'Use when ...' clause listing natural triggers (e.g., 'Use when automating Apaleo reservations, rates, availability, or booking workflows').

Replace the generic 'Automate Apaleo tasks' with 2-3 concrete actions (e.g., 'manage reservations, sync rates, pull availability reports') to lift specificity.

Include task-level synonyms users actually say (reservations, bookings, rates) alongside 'Apaleo' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Apaleo tasks via Rube MCP (Composio)") but the only action stated is the generic "Automate Apaleo tasks"; "Always search tools first for current schemas" is a process instruction rather than a concrete capability, so actions are minimal/generic.

2 / 5

Completeness

A clear 'what' is present ("Automate Apaleo tasks via Rube MCP"), but there is no 'Use when...' or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

"Apaleo tasks" is a natural term a user would say, but the rest is technical jargon (Rube MCP, Composio, schemas) and task-specific variations (reservations, rates, bookings) are absent, matching 'some relevant keywords but missing common variations.'

3 / 5

Distinctiveness Conflict Risk

Apaleo is a specific named PMS and Rube MCP a specific integration, giving a clear niche with minimal conflict risk; minor overlap remains with other Composio/Rube automation skills, so it is mostly distinct rather than fully so.

4 / 5

Total

12

/

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