Get the FREE Ultimate OpenClaw Setup Guide →

canvas-course-qc

Scanned
npx machina-cli add skill vishalsachdev/canvas-mcp/canvas-course-qc --openclaw
Files (1)
SKILL.md
5.6 KB

Canvas Course QC

Automated quality checklist for Learning Designers to verify a Canvas course is ready for students. Runs structure, content, publishing, and completeness checks — then reports issues by priority.

Prerequisites

  • Canvas MCP server must be running and connected.
  • Authenticated user must have instructor, TA, or designer role in the target course.
  • Best run before the semester starts or before publishing a course to students.

Steps

1. Identify Target Course

Ask the user which course to QC. Accept a course code, Canvas ID, or course name.

If not specified, prompt:

Which course would you like to quality-check?

Use list_courses to look up available courses if needed.

2. Retrieve Course Structure

Call get_course_structure(course_identifier) to get the full module-to-items tree in one call.

This returns all modules with their items, publishing states, and summary statistics.

3. Run Structure Checks

Analyze the module tree for structural issues:

CheckPriorityWhat to Look For
Empty modulesWarningModules with 0 items (confusing to students)
Naming consistencySuggestionDo all modules follow the same pattern? (e.g., "Week N:", "Unit N:")
Module countSuggestionDoes it match expected count for course length?
Item orderingSuggestionSubHeaders present for organization?

4. Run Content Checks

Call list_assignments(course_identifier) and check each assignment:

CheckPriorityWhat to Look For
Missing due datesBlockingGraded assignments without a due_at date
Missing descriptionsWarningAssignments with empty or null description
Missing pointsWarningAssignments without points_possible set
Date sequencingWarningDue dates that don't follow module order
Rubric coverageSuggestionGraded assignments without an associated rubric

For pages, check if any pages in modules have empty body content using get_page_content for pages flagged in the structure.

5. Run Publishing Checks

Using the structure data:

CheckPriorityWhat to Look For
Ghost itemsBlockingPublished items inside unpublished modules (invisible to students)
Unpublished modulesWarningModules that may need publishing before semester
No front pageWarningCourse has no front page set

Check for front page by calling list_pages(course_identifier) and looking for front_page: true.

6. Run Completeness Checks

Compare module structures to find inconsistencies:

CheckPriorityWhat to Look For
Inconsistent structureWarningMost modules have 4 items but some only have 1
Missing item typesSuggestionMost modules have an Assignment but some don't

Build a "typical module" profile from the most common item-type pattern, then flag modules that deviate.

7. Generate QC Report

Present results grouped by priority:

## Course QC Report: [Course Name]

### Summary
- Modules: 15 | Items: 67 | Assignments: 15 | Pages: 20
- Issues found: 3 blocking, 5 warnings, 2 suggestions

### Blocking Issues (fix before publishing)
1. Assignment "Final Project" has no due date
2. Published "Week 5 Quiz" is inside unpublished "Week 5" module (invisible to students)
3. Assignment "Midterm" has no due date

### Warnings (should fix)
1. 2 empty modules: "Week 14", "Week 15"
2. 3 assignments missing descriptions: HW 3, HW 7, HW 12
3. No front page set for course
4. Due dates out of order: Week 8 assignment due before Week 7
5. "Week 3" module has 1 item while typical modules have 4

### Suggestions (nice-to-have)
1. Module naming: 13/15 use "Week N:" pattern but "Midterm Review" and "Final Review" don't
2. 5 graded assignments have no rubric attached

8. Offer Follow-up Actions

After presenting the report, offer actionable next steps:

Would you like me to:

  1. Auto-fix publishing -- Publish all unpublished modules (with confirmation)
  2. Show details -- Expand on a specific issue
  3. Run accessibility audit -- Check WCAG compliance (uses canvas-accessibility-auditor skill)
  4. Check another course

For auto-fix, use update_module or bulk_update_pages with user confirmation before each batch.

MCP Tools Used

ToolPurpose
list_coursesFind available courses
get_course_structureFull module tree with items
list_assignmentsAssignment details for content checks
get_assignment_detailsDeep-dive on flagged assignments
list_pagesCheck for front page
get_page_contentVerify pages have content
list_all_rubricsCheck rubric coverage
update_moduleAuto-fix: publish modules
bulk_update_pagesAuto-fix: publish pages

Example

User: "QC check for BADM 350"

Agent: Runs all checks, outputs the prioritized report.

User: "Fix the publishing issues"

Agent: Publishes the 2 unpublished modules after confirmation.

Notes

  • This skill is designed for Learning Designers who manage course structure before students access it.
  • Run this before each semester or after major content updates.
  • Pairs well with canvas-accessibility-auditor for comprehensive course review.

Source

git clone https://github.com/vishalsachdev/canvas-mcp/blob/main/skills/canvas-course-qc/SKILL.mdView on GitHub

Overview

Automated quality checklist ensuring a Canvas course is ready for students. It audits structure, content, publishing state, and completeness, then reports issues by priority to guide fixes.

How This Skill Works

Identify the target course using user input, then fetch the full module-to-items tree with get_course_structure(course_identifier). The tool then runs a series of checks across modules, items, pages, and publication states—covering structure, content, publishing, and completeness—and reports findings by priority to guide what to fix before publishing.

When to Use It

  • QC a course
  • is this course ready
  • pre-semester check
  • quality review
  • course updates and audits

Quick Start

  1. Step 1: Identify the target course to QC
  2. Step 2: Retrieve the course structure with get_course_structure(course_identifier)
  3. Step 3: Run the checks and review the QC report

Best Practices

  • Ensure Canvas MCP server is running and connected
  • Authenticate as instructor, TA, or designer in the target course
  • Run QC before publishing or at semester start
  • Review module structure for naming consistency and item count
  • Check critical gaps: due dates, descriptions, points, and linked rubrics

Example Use Cases

  • QC a new Intro to Psychology course before the term starts
  • Audit a mid-term course to ensure no front page is missing and no ghost items
  • Perform a pre-semester QC for a multi-module science course
  • Run rubric coverage checks on graded assignments in a research methods course
  • Identify empty modules and non-sequenced due dates in a published course

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers