CtrlK
BlogDocsLog inGet started
Tessl Logo

canva-automation

Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.

52

Quality

59%

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

Quality

Content

56%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid structural overview of Canva automation workflows with clear tool sequences and useful pitfall warnings. Its main weaknesses are the lack of concrete, executable examples (actual MCP call syntax with real parameters) and some redundancy between per-workflow pitfalls and the consolidated 'Known Pitfalls' section. The content would benefit from concrete invocation examples and splitting detailed workflow content into separate files.

Suggestions

Add concrete, executable MCP tool call examples with actual parameter values and expected response structures for at least the most common workflows (e.g., export, upload).

Remove the redundant 'Known Pitfalls' section or consolidate it with per-workflow pitfalls to reduce repetition and improve conciseness.

Add explicit error handling guidance for failed async jobs (what to check, whether to retry, how to surface errors to the user).

Remove the vacuous 'When to Use' section at the end, which adds no information beyond the description.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary verbosity. The 'Known Pitfalls' section repeats information already stated in individual workflow pitfalls. The 'When to Use' section at the end is vacuous. Some parameter descriptions are obvious (e.g., 'name: Folder name'). However, the quick reference table is efficient and the overall structure avoids explaining basic concepts.

3 / 5

Actionability

The skill provides tool names, parameter lists, and sequences, but lacks executable code examples. The 'Async Job Pattern' and 'ID Resolution' sections use pseudocode-style numbered lists rather than actual MCP call examples with concrete arguments. There are no copy-paste ready tool invocations showing exact parameter formats or response structures, which would be needed for Claude to confidently execute these workflows.

3 / 5

Workflow Clarity

Workflows are clearly sequenced with labeled steps, required/optional annotations, and the async job pattern explicitly calls out polling requirements. The export workflow includes a prerequisite step. However, the polling steps lack explicit validation checkpoints (e.g., what to do on 'failed' status beyond noting it exists), and there's no explicit error recovery guidance for most workflows beyond the general async pattern.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table, but at ~200 lines it's a monolithic file with no bundle files to offload detailed content. The individual workflow sections, common patterns, and known pitfalls could benefit from being split into separate reference files. For a skill with this many workflows, having everything inline is borderline too much for a single SKILL.md.

3 / 5

Total

13

/

20

Passed

Description

62%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 identifies a clear niche (Canva automation via Rube MCP) and lists several concrete capabilities, making it distinctive. However, it lacks an explicit 'Use when...' clause, which is critical for Claude's skill selection, and the trigger terms lean toward technical jargon rather than natural user language.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Canva designs, creating graphics, exporting Canva files, or managing Canva brand assets.'

Include more natural user-facing trigger terms and synonyms such as 'create a design', 'graphic design', 'download from Canva', 'Canva presentation', or 'social media graphics'.

DimensionReasoningScore

Specificity

Lists several specific actions: designs, exports, folders, brand templates, autofill. Also mentions searching tools for current schemas. Minor gaps in that these are listed as nouns rather than fully described actions, but coverage is reasonable.

4 / 5

Completeness

The 'what' is reasonably clear (automate Canva tasks including designs, exports, folders, brand templates, autofill). However, there is no explicit 'when' clause — no 'Use when...' guidance for Claude to know when to select this skill. This caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes 'Canva', 'designs', 'exports', 'folders', 'brand templates', 'autofill' which are relevant keywords. However, it's missing natural user phrases like 'create a design', 'download from Canva', 'Canva presentation', or synonyms. 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

3 / 5

Distinctiveness Conflict Risk

Very distinct niche: Canva automation via a specific MCP integration (Rube/Composio). The combination of 'Canva' and the specific tool chain makes it highly unlikely to conflict with other skills.

5 / 5

Total

15

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.