CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

canvas-automation

Automate Canvas tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

68%

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

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-organized, actionable guide with concrete parameterized tool-call patterns, a clear three-step workflow, and pre-flight validation checkpoints. Main gaps are the absence of an error-recovery loop after tool execution, minor redundancy around the search-first rule, and placeholder-only execution examples with no worked end-to-end call.

Suggestions

Add a short error-recovery step after Step 3: how to interpret RUBE_MULTI_EXECUTE_TOOL failures, retry with corrected arguments from the search schema, and re-check the connection when auth errors appear.

Consolidate the repeated 'always search tools first' guidance into one place (Known Pitfalls) and drop the 'Powered by Composio' footer to save tokens.

Include one complete worked example of a RUBE_MULTI_EXECUTE_TOOL call with realistic argument values so the pattern is copy-paste ready, not just placeholder-shaped.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what Canvas or MCP is, and each section earns its place. It is not anchor 5 because "Always search first" is repeated in Prerequisites, Tool Discovery, Step 1, and Known Pitfalls, and the "Powered by Composio" footer line adds no operational value.

4 / 5

Actionability

Concrete call blocks with real parameters are given for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL. It is not anchor 5 because the execution example uses placeholders ("TOOL_SLUG_FROM_SEARCH", "/* schema-compliant args from search results */") rather than one complete worked example; the placeholder approach is justified by the schemas-change rule, keeping it above anchor 3.

4 / 5

Workflow Clarity

The three-step sequence (discover tools → check connection → execute) is clear, with pre-flight validation checkpoints (confirm ACTIVE before running workflows, check pagination tokens). It is not anchor 5 because there is no post-execution feedback loop (what to do when RUBE_MULTI_EXECUTE_TOOL fails or returns errors), which matters since multi-execute is a batch-style operation; the batch cap at 3 does not apply because validation steps are present, not missing.

4 / 5

Progressive Disclosure

No bundle files exist and the single file is well-organized with clear sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) plus a clearly signaled external docs link; nothing inlined here clearly belongs in a separate file. It is not anchor 5 because there is no reference structure at all — the anchor-5 pattern of well-signaled one-level-deep references is absent, and the file runs ~85 lines where a reference split (e.g. a pitfalls/examples file) could help.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies a distinct niche (Canvas automation via Rube MCP) but reads more like an internal behavioral reminder than a skill description: it lists no concrete Canvas capabilities and provides no "use when" trigger guidance. Trigger-term coverage rests on the single word "Canvas". Scores are middling across specificity, triggers, and completeness.

Suggestions

Add 2-3 concrete capabilities to the description, e.g. "Submit assignments, post announcements, manage courses and grades in Canvas LMS via Rube MCP (Composio)."

Add an explicit trigger clause: "Use when the user asks to automate Canvas LMS tasks — assignments, courses, announcements, or grades."

Include natural synonyms such as "Canvas LMS" so users who say the full product name match the skill; keep the 'search tools first' reminder in the body instead of the description.

DimensionReasoningScore

Specificity

"Automate Canvas tasks via Rube MCP" names the domain but the only action is the generic "Automate Canvas tasks"; the rest of the sentence ("Always search tools first for current schemas") is a behavioral instruction, not a capability. It does not list any concrete Canvas actions (e.g. submit assignments, post announcements, pull grades), matching anchor 2 rather than anchor 3.

2 / 5

Completeness

The 'what' is stated (automate Canvas tasks via Rube MCP) but is high-level, and there is no "Use when..." clause or equivalent trigger guidance anywhere in the description. Per the rubric guideline, a missing 'when' clause caps completeness at 3, which this matches; it is above anchor 2 because the 'what' is present and domain-specific.

3 / 5

Trigger Term Quality

"Canvas" is a genuine natural keyword a user would say, but the description misses common variations and synonyms ("Canvas LMS", "assignments", "courses", "grades", "announcements"), and "Rube MCP (Composio)" is technical jargon users would not say. This matches anchor 3 (some relevant keywords, missing variations) better than 2 (the keyword is specific, not generic) or 4 (coverage is too thin).

3 / 5

Distinctiveness Conflict Risk

The Canvas-LMS-via-Rube-MCP combination is a clear niche with distinct triggers and would rarely fire the wrong skill. It is not anchor 5 because "Automate Canvas tasks" could still overlap with generic automation or other LMS-related skills, but overlap risk is minor.

4 / 5

Total

12

/

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.

Validation — 15 / 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

ComposioHQ/awesome-claude-skills

Path

composio-skills/canvas-automation/SKILL.md

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.