CtrlK
BlogDocsLog inGet started
Tessl Logo

canva

Canva integration. Manage data, records, and automate workflows. Use when the user wants to interact with Canva data.

56

Quality

65%

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

Quality

Content

67%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 highly actionable with concrete CLI commands and a well-sequenced connection workflow including validation checkpoints, but it is held back by a padded intro explaining Canva and a vague, dangling overview section.

Suggestions

Cut the opening paragraph describing what Canva is and the 'Canva Overview' filler; Claude already knows the product.

Resolve the dangling 'Step 2' reference by adding a matching labeled section or removing the cross-reference.

In 'Popular actions', list a few concrete example Canva actions (e.g. list designs, get a page, render an export) instead of only re-stating the discovery command.

DimensionReasoningScore

Conciseness

The opening paragraph explaining what Canva is ('user-friendly graphic design platform... extensive template library') and the thin 'Canva Overview' filler ('Use action names and parameters as needed.') over-explain concepts Claude already knows, though the bulk of the CLI commands are efficient.

3 / 5

Actionability

Provides copy-paste ready commands for install, auth, connection, action search/run, and proxy requests plus a flag table, with only a minor gap: the 'Popular actions' section rediscovers via list rather than naming concrete Canva actions.

4 / 5

Workflow Clarity

A clear install→auth→connect→wait→search→run sequence is present with state-based polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a retry loop, but the 'skip to Step 2' reference has no matching labeled section.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file content is well-organized into clearly headed sections. At ~140 lines it exceeds the simple-skill threshold, and the thin 'Canva Overview' section is a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

62%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 answers both what and when and is clearly Canva-scoped, but relies on generic action verbs rather than concrete Canva capabilities and lacks richer natural trigger terms.

Suggestions

Replace generic verbs with concrete Canva actions, e.g. 'Create and edit designs, manage brand kits, browse templates, and organize folders'.

Expand the trigger clause with natural phrasing users say, e.g. 'Use when the user wants to create or edit Canva designs, manage templates, or work with Canva data'.

Mention key Canva nouns (designs, pages, brand kits, templates, folders) so the skill triggers on a wider range of natural requests.

DimensionReasoningScore

Specificity

Names the domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Canva-specific capabilities like designs, pages, or templates, so it is not comprehensive.

3 / 5

Completeness

Both 'what' ('Canva integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Canva data') are present, but the trigger clause could be more explicit and specific.

4 / 5

Trigger Term Quality

Includes the natural keyword 'Canva' and the phrase 'interact with Canva data', but misses common variations and synonyms users would actually say (designs, templates, brand kits, presentations).

3 / 5

Distinctiveness Conflict Risk

The Canva scope and 'interact with Canva data' trigger make it mostly distinct, though the generic 'manage data, records, automate workflows' framing creates minor overlap risk with other data-integration skills.

4 / 5

Total

14

/

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.

Validation15 / 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
membranedev/application-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.