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

70%

Does it follow best practices?

Impact

79%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/canva-automation/SKILL.md

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 MCP automation guide with clear sequenced workflows, explicit async-polling checkpoints, and a useful quick-reference table. It is efficient and organized with only minor conciseness and disclosure gaps.

Dimension	Reasoning	Score
Conciseness	Efficient and well-organized, assuming competence; minor repetition of the async-polling guidance across sections and Known Pitfalls keeps it just below the lean 5 anchor.	4 / 5
Actionability	Concrete tool slugs, exact parameters, status values, poll intervals, and supported formats provide mostly executable guidance with minor gaps (no full request/response payloads).	4 / 5
Workflow Clarity	Numbered tool sequences with explicit validation/polling checkpoints ("Confirm connection status shows ACTIVE", "MUST poll job status") and success/failed feedback loops; minor validation gaps versus the 5 anchor.	4 / 5
Progressive Disclosure	Single-file skill with clear one-level section structure (Prerequisites, Setup, Workflows, Patterns, Pitfalls, Quick Reference) and easy navigation; no bundle files to assess, so just below the 5 anchor's split-file ideal.	4 / 5
	Total	16 / 20 Passed

Description

66%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 is specific and well-scoped to a distinct Canva-automation niche with good trigger keywords, but it lacks an explicit "Use when..." trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user wants to create, export, or organize Canva designs, or fill brand templates').

Include a couple of natural synonyms/variants (e.g., 'Canva designs, presentations, social posts, exports') to broaden trigger-term coverage toward the 5 anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("designs, exports, folders, brand templates, autofill") tied to a named toolkit, with only minor coverage gaps; not quite the comprehensive multi-action list of the 5 anchor.	4 / 5
Completeness	Clear "what" is present, but there is no explicit "Use when..." trigger clause; the judging guideline caps completeness at 3 for a missing trigger clause.	3 / 5
Trigger Term Quality	Good natural-term coverage ("Canva", "designs", "exports", "brand templates", "autofill", "folders") users would actually say, with a few common variations/synonyms missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to Canva automation via Rube MCP (Composio) with distinct triggers and minimal overlap risk, sitting just below the clearly-niche 5 anchor.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/canva-automation/SKILL.md
Commit: a9fa86d

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.