CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

appointo-automation

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

56

Quality

70%

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

Quality

Content

75%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 a tight, well-structured workflow guide with concrete Rube MCP invocations and explicit connection-validation checkpoints. Its main weaknesses are minor: a duplicated discovery section and placeholder-based rather than literal-copy-paste examples.

Suggestions

Consolidate the "Tool Discovery" section with "Step 1: Discover Available Tools" to remove the duplicated RUBE_SEARCH_TOOLS guidance.

Add an explicit error-recovery step after RUBE_MULTI_EXECUTE_TOOL (e.g. inspect error responses, adjust arguments per the schema, and retry) to reach a 5 on workflow clarity.

Provide at least one fully resolved example invocation with real-shaped values to lift actionability from mostly-executable to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean with no padding or over-explanation of known concepts, but the "Tool Discovery" section repeats the same RUBE_SEARCH_TOOLS guidance later restated as "Step 1: Discover Available Tools", a minor redundancy that keeps it just below the lean/efficient anchor of 5.

4 / 5

Actionability

Concrete tool invocations with parameter blocks (RUBE_SEARCH_TOOLS queries/session, RUBE_MULTI_EXECUTE_TOOL tools/memory/session_id) are provided, but they use placeholders like "your_session_id" and "TOOL_SLUG_FROM_SEARCH" rather than being literally copy-paste ready, matching the mostly-executable anchor at 4.

4 / 5

Workflow Clarity

A clearly sequenced setup and three-step core workflow is present with validation checkpoints (confirm ACTIVE connection before executing), so the batch-operation cap does not apply; it stops short of 5 only because there is no explicit error-recovery feedback loop for failed executions.

4 / 5

Progressive Disclosure

The body is well organized into headed sections plus a quick-reference table and carries no external bundle files, but the duplicated discovery content across two sections is a minor organization gap that prevents a 5.

4 / 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 concise and names a clear niche, but it omits any explicit trigger/"Use when" guidance and relies on technical jargon rather than natural user phrasings. These gaps cap specificity and completeness at 3 despite strong distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to automate Appointo bookings, appointments, or scheduling tasks."

Include natural user-facing terms like "bookings", "appointments", and "scheduling" alongside the technical "Appointo"/"Rube MCP" labels.

Enumerate one or two concrete actions (e.g. "create, list, and update appointments") to lift specificity above 3.

DimensionReasoningScore

Specificity

Names the domain ("Automate Appointo tasks") plus one concrete directive ("Always search tools first"), but does not enumerate the specific appointment operations it covers, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

The "what" is clear (automate Appointo via Rube MCP), but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes domain terms ("Appointo", "Rube MCP", "Composio") but these skew toward technical jargon and miss the natural user phrasings (bookings, appointments, scheduling) users would actually say, matching the "some relevant keywords but missing variations" anchor.

3 / 5

Distinctiveness Conflict Risk

"Appointo" is a distinct niche and the "via Rube MCP (Composio)" qualifier narrows it further, giving mostly-distinct activation with only minor overlap risk against other Rube/Composio toolkit 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/appointo-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.