canva-automation
Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.
64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 effectively identifies specific Canva capabilities and has strong distinctiveness through platform-specific naming. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and the trigger terms could be expanded to include more natural user language variations.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user mentions Canva, creating graphics, social media designs, or needs to work with Canva templates'
Expand trigger terms to include natural user language: 'Canva designs', 'social media graphics', 'create a poster', 'design templates'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designs, exports, folders, brand templates, autofill' - these are distinct, actionable capabilities within the Canva domain. | 3 / 3 |
Completeness | Describes what it does (automate Canva tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The instruction to 'search tools first' is implementation guidance, not selection guidance. | 1 / 3 |
Trigger Term Quality | Includes 'Canva' as a strong trigger term and domain-specific terms like 'designs', 'exports', 'brand templates', but missing common user phrases like 'create a design', 'Canva graphic', or file extensions users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'Canva' and 'Rube MCP (Composio)' create a very clear niche - this is unlikely to conflict with other skills as it targets a specific platform and integration method. | 3 / 3 |
Total | 9 / 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 skill provides comprehensive coverage of Canva automation workflows with excellent structure and clear sequencing. However, it lacks executable code examples (relying on pseudocode patterns) and could be more concise by eliminating redundant explanations of async patterns. The actionability would significantly improve with actual MCP tool call syntax examples.
Suggestions
Add executable code examples showing actual MCP tool call syntax (e.g., how to call RUBE_SEARCH_TOOLS and parse the response)
Consolidate async job pattern explanation - mention it once in Common Patterns and reference that section from workflows instead of repeating in each
Move the Quick Reference table to a separate REFERENCE.md file and link to it, reducing the main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the async job pattern is explained multiple times across workflows and then again in Common Patterns. The Quick Reference table duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The 'Async Job Pattern' and 'ID Resolution' sections use pseudocode-style descriptions rather than actual API call examples with concrete syntax. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, explicit [Required]/[Optional] markers, and consistent structure. Async operations include explicit polling requirements and validation checkpoints (poll until success/failed). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is somewhat monolithic at ~200 lines. The Quick Reference table could be a separate file, and there are no links to detailed documentation for individual workflows. | 2 / 3 |
Total | 9 / 12 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.
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 | |
- 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.