canvas-integration_skill

This skill enables you to manage and interact with Canvas data using the Membrane CLI, simplifying authentication and action execution.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill canvas-integration

  • _meta.json281 B
  • SKILL.md5.3 KB

Overview

This skill integrates with the Canvas learning management system to manage courses, assignments, modules, users, and submissions. It uses the Membrane CLI to handle authentication and to run pre-built Canvas actions or proxy raw API requests. The skill is designed to let you list, create, update, and retrieve common Canvas resources without handling tokens or pagination manually.

How this skill works

The skill communicates with Canvas through Membrane: you create a Membrane connection for Canvas and then run predefined actions or proxy requests. Membrane handles authentication, token refresh, pagination, and error handling. Use the Membrane CLI to discover available actions, run them with input JSON, or send custom HTTP requests that Membrane forwards to the Canvas API.

When to use it

  • When you need to list or retrieve Canvas courses, assignments, modules, users, or submissions.
  • When you want to create or update Canvas resources programmatically without managing API keys or OAuth tokens.
  • When you prefer using pre-built actions (pagination and error handling included) rather than direct API calls.
  • When you need to run a custom Canvas API request not covered by existing actions via a proxy.

Best practices

  • Prefer Membrane pre-built actions for common operations to reduce token usage and avoid implementing pagination or retries yourself.
  • Run action discovery (membrane action list --intent=QUERY) before writing custom calls to find existing actions that meet your needs.
  • Never request or store raw Canvas API keys—create and reuse a Membrane connection so credentials are managed server-side.
  • For headless environments, use the login URL flow and complete the login with the provided code to avoid interactive browser requirements.
  • Use proxy requests only when an action does not exist; include proper method, headers, and query/path params when calling membrane request.

Example use cases

  • List all courses and then fetch assignments for a selected course to build a course dashboard.
  • Create a new assignment or module programmatically as part of a course provisioning workflow.
  • Retrieve submissions for an assignment to trigger grading automation or export results.
  • Sync user lists between an institutional directory and Canvas by listing users in an account or course.
  • Run a custom Canvas API endpoint through the Membrane proxy to access an endpoint not covered by actions.

FAQ

No. Membrane manages authentication and token refresh for you once you create a Canvas connection.

How do I discover what actions are available?

Use membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json to see available actions and their input schemas.

Can I call endpoints that are not implemented as actions?

Yes. Use membrane request CONNECTION_ID /path/to/endpoint with appropriate flags for method, headers, data, and query parameters.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational