CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cardly-automation

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/cardly-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, actionable guide with a clear three-step workflow, explicit connection validation, and a useful pitfalls/quick-reference section. Its weaknesses are modest: some repeated emphasis, placeholder arguments that can't be made copy-paste ready by design, and no execution-failure recovery guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but 'Always call RUBE_SEARCH_TOOLS first' is repeated roughly four times (Prerequisites, Tool Discovery, Step 1, Known Pitfalls) and 'No API keys needed — just add the endpoint and it works' could be trimmed — minor over-explanation, not the 5-anchor's 'every token earns its place'.

4 / 5

Actionability

Tool calls are shown with concrete parameter structures (queries, session, toolkits, tools arrays) and a quick-reference table, but placeholders like "TOOL_SLUG_FROM_SEARCH" and {/* schema-compliant args */} keep them from being fully copy-paste ready — mostly executable with minor gaps.

4 / 5

Workflow Clarity

The discover → check connection → execute sequence is clear with an explicit ACTIVE-status checkpoint and auth-link recovery, plus a pagination continuation check; however there is no error-recovery loop for failed tool executions, so it falls short of the 5 anchor's 'feedback loops for error recovery'.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~85-line body is well organized with clear section headers and a quick-reference table, all content appropriately inline. It exceeds the 50-line simple-skill threshold, so 'good structure with minor organization gaps' (4) is the best fit rather than 5.

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 establishes a clear niche (Cardly automation via Rube MCP) but is thin: it names no concrete capabilities, omits any 'use when' trigger guidance, and relies on a single product-name keyword. Adding specific actions and an explicit trigger clause would materially improve it.

Suggestions

List 2-4 concrete Cardly operations (e.g., 'send cards, manage contacts, review delivery status') instead of the generic 'Automate Cardly tasks'.

Add a 'Use when...' clause, e.g., 'Use when the user mentions Cardly, wants to send cards or manage their Cardly account'.

Include natural task-level trigger phrases/synonyms (card sending, greetings, client gifts) alongside the product name, since 'Rube MCP (Composio)' is jargon users won't say.

DimensionReasoningScore

Specificity

"Automate Cardly tasks" names the domain but the action is generic — no concrete operations (e.g., sending cards, managing contacts) are listed, matching the 'Processes PDF files' anchor rather than the 1-2-concrete-actions level.

2 / 5

Completeness

The 'what' is clear ("Automate Cardly tasks via Rube MCP"), but there is no 'when' / 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"Cardly" is a natural keyword, but "Rube MCP (Composio)" is technical jargon and no task-level synonyms or variations users would actually say are present.

3 / 5

Distinctiveness Conflict Risk

"Cardly" is a distinct niche trigger with minimal conflict risk, though sibling Rube/Composio toolkit skills share the identical "Automate X via Rube MCP" pattern, creating minor 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/cardly-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.