CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ascora-automation

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

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/ascora-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 well-structured, largely executable guide with explicit connection-validation checkpoints and a useful quick-reference table. Its main gaps are a slightly redundant search-tools block and the absence of a post-execution validation/error-recovery loop for bulk operations.

DimensionReasoningScore

Conciseness

The body is lean with code blocks and clear sections and assumes Claude's competence; minor trimming is possible (the RUBE_SEARCH_TOOLS pattern recurs across Tool Discovery and Core Workflow Step 1), placing it at 'Efficient; minor instances of over-explanation that could be trimmed' rather than a fully lean 5.

4 / 5

Actionability

Concrete tool invocations with parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) plus a Quick Reference table give mostly executable guidance; it stops short of 5 because arguments use necessary placeholders ('TOOL_SLUG_FROM_SEARCH', 'your_session_id') rather than fully copy-paste-ready examples.

4 / 5

Workflow Clarity

Setup and Core Workflow steps are clearly sequenced with explicit checkpoints ('Confirm connection status shows ACTIVE before running any workflows', 'Verify ... ACTIVE status before executing tools'); it does not reach 5 because the bulk-execute step lacks an explicit result-validation / error-recovery feedback loop.

4 / 5

Progressive Disclosure

Content is well-organized into headers (Prerequisites, Setup, Tool Discovery, Core Workflow Pattern, Known Pitfalls, Quick Reference) with no nested references and a single one-level external docs link; at ~84 lines it exceeds the under-50-line simple-skill exception that would allow a 5, so it lands at 'Good structure; most content is appropriately placed'.

4 / 5

Total

16

/

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 clear, distinct niche and a relevant trigger term but offers only a generic action and omits any explicit 'Use when...' trigger guidance, capping completeness. It is functional but lacks the concrete capability list and trigger phrasing of top-tier descriptions.

Suggestions

Add 1-2 concrete actions, e.g. 'create, update, and query Ascora records' instead of the generic 'Automate Ascora tasks'.

Append an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to automate or run Ascora workflows.'

Include common synonyms or surface the primary entity (e.g. 'Ascora jobs/bookings') to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Automate Ascora tasks via Rube MCP' names the domain but the action 'Automate tasks' is generic and minimal, matching the anchor 'Names the domain but actions are minimal or generic'; the second sentence ('Always search tools first for current schemas') is a precaution, not a capability, so it does not push this to 3.

2 / 5

Completeness

A clear 'what' is present ('Automate Ascora tasks via Rube MCP (Composio)') but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms 'Ascora', 'Rube MCP', and 'Composio' are relevant product-specific keywords a user of the tool would say, but coverage lacks synonyms or variations, matching 'Some relevant keywords but missing common variations or synonyms'; it is above 2 because 'Ascora' is a genuine natural trigger rather than generic jargon.

3 / 5

Distinctiveness Conflict Risk

The niche 'Ascora via Rube MCP (Composio)' is mostly distinct with only minor overlap risk against other automation skills; it does not reach 5 because 'tasks' is generic enough to invite some overlap.

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