canva-automation

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

1.51x

Quality

65%

Does it follow best practices?

Impact

79%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/canva-automation/SKILL.md

Quality

Discovery

67%

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 does a good job listing specific Canva-related capabilities and is clearly distinguishable from other skills due to its Canva + Rube MCP focus. However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms could be more user-facing rather than including technical integration names.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Canva designs, exporting graphics, managing Canva folders, or working with brand templates.'

Include more natural user-facing trigger terms such as 'graphic design', 'create a poster', 'download design', or 'Canva project' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: designs, exports, folders, brand templates, autofill. Also includes a procedural instruction ('Always search tools first for current schemas').	3 / 3
Completeness	The 'what' is well covered (automate Canva tasks including designs, exports, folders, brand templates, autofill), but there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Canva', 'designs', 'exports', 'folders', 'brand templates', 'autofill', but misses common user variations like 'create a design', 'download from Canva', 'graphic design', or file format terms. 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Canva-specific tasks via a specific MCP integration (Rube/Composio), making it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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

This is a solid reference skill for Canva automation via Rube MCP with clear workflow sequences, good async operation handling, and useful pitfall documentation. Its main weaknesses are moderate verbosity from repeated information across sections and the lack of concrete executable examples showing actual MCP call syntax. The content would benefit from being trimmed and having actual invocation examples added.

Suggestions

Add at least one concrete, copy-paste-ready MCP call example (e.g., showing the exact RUBE_SEARCH_TOOLS invocation with parameters) to improve actionability.

Consolidate repeated async polling guidance into the Common Patterns section only, and reference it from individual workflows instead of restating it in each pitfalls section.

Remove the Quick Reference table or the detailed workflow sections—having both is redundant. The table could replace verbose parameter listings if workflows are kept lean.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (async polling mentioned in nearly every workflow and again in Known Pitfalls), and some information Claude could infer (e.g., 'Supported formats include PNG, JPG, SVG, MP4, GIF') adds bulk without unique value. The quick reference table at the end largely duplicates the workflow sections.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code examples or concrete MCP call syntax—everything is described at a pseudocode/prose level. The async job pattern is described in numbered steps rather than showing an actual invocation. The instruction to 'always call RUBE_SEARCH_TOOLS first' is actionable but the actual call format is never shown.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps, explicit required/optional annotations, and validation checkpoints (polling for async job completion, checking status values for success/failed). The async job pattern is explicitly documented with a feedback loop (poll -> check -> extract result). Export and upload workflows both include mandatory polling steps before proceeding.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and a logical progression from setup to workflows to patterns to quick reference. However, with no bundle files, all content is inline in a single long document (~180 lines). The detailed pitfalls and parameters for each workflow could be split into separate reference files, with the SKILL.md serving as a leaner overview. The external link to Composio docs is helpful but the skill itself is monolithic.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: 74c7031

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.