تشغيل أي مهارة في Manus بنقرة واحدة

canvas-info

Research and answer questions about Canvas LMS courses using the canvaslms CLI. Use proactively when: (1) user asks about course content, assignments, pages, grades, deadlines, or announcements, (2) user mentions a Canvas course name or course code, (3) user asks "what assignments/pages/modules are in [course]?", (4) user wants to find specific course materials or check deadlines. This skill is read-only; to create quiz content, use the canvas-quiz skill instead.

تشغيل في Manus

نظرة عامة

أمر التثبيت

npx skills add https://github.com/dbosk/claude-skills --skill canvas-info

انسخ والصق هذا الأمر في Claude Code لتثبيت المهارة

المصدر

dbosk/claude-skills

النجوم١

التفرعات٠

آخر تحديث١١ فبراير ٢٠٢٦ في ١٠:٢٦

SKILL.md

readonly

name

canvas-info

description

Canvas Course Information Research

Overview

The canvaslms CLI provides read-only access to Canvas LMS course data: assignments, pages, modules, discussions, announcements, grades, quizzes, and calendar events. This skill teaches a research workflow for answering user questions about their courses.

For detailed options on any subcommand, run canvaslms <subcommand> -h.

Research Workflow

Follow these steps when answering a Canvas-related question:

Step 1: Identify the Course

canvaslms courses              # List all courses
canvaslms courses "regex"      # Filter by name/code (case-insensitive regex)

Note the course ID from the output. Use it with -c <id> in subsequent commands.

Step 2: Explore Course Structure

Choose the right entry point based on the question:

Question type	Start with
"What's in this course?"	`canvaslms modules list -c <id>`
"What assignments exist?"	`canvaslms assignments list -c <id>`
"Any announcements?"	`canvaslms discussions list -c <id> -t announcement`
"What pages are available?"	`canvaslms pages list -c <id>`
"What are the deadlines?"	`canvaslms calendar -c <id>`
"How did students do?"	`canvaslms results -c <id>`

Step 3: Drill into Content

Use view subcommands to read specific items:

canvaslms modules view -c <id> -m "module regex"
canvaslms pages view -c <id> -p "page regex"
canvaslms assignments view -c <id> -a "assignment regex"
canvaslms discussions view -c <id> -d "discussion regex"

The view commands output full content (markdown for pages, HTML for assignments). The list commands output tab-delimited CSV summaries.

Step 4: Refine with Filters

Most commands accept regex filters and additional flags. Run canvaslms <subcommand> -h to discover available filters for each command.

Common refinement patterns:

Combine course + item filters: -c "DD2520" -a "lab"
Filter by module: -c <id> -m "week 3"
Filter submissions by user: canvaslms submissions -c <id> -u "username"

Step 5: Synthesize and Answer

After gathering data:

Quote relevant content directly when answering
Summarize lists into readable format (tables, bullets)
If data seems stale, suggest re-running with --no-cache
Provide the course/assignment/page names so the user can navigate in Canvas

Quick Reference

To find...	Command	Key flags
All courses	`canvaslms courses`	regex filter, `-i` for ID only
Course modules	`canvaslms modules list`	`-c`, `-m`
Module contents	`canvaslms modules view`	`-c`, `-m`
Assignments	`canvaslms assignments list`	`-c`, `-a`, `-m`
Assignment details	`canvaslms assignments view`	`-c`, `-a`
Wiki pages	`canvaslms pages list`	`-c`, `-p`, `-m`
Page content	`canvaslms pages view`	`-c`, `-p`
Announcements	`canvaslms discussions list`	`-c`, `-t announcement`
Discussions	`canvaslms discussions list`	`-c`, `-t discussion`
Discussion content	`canvaslms discussions view`	`-c`, `-d`
Quizzes	`canvaslms quizzes list`	`-c`, `-q`
Submissions	`canvaslms submissions`	`-c`, `-a`, `-u`
Grades/results	`canvaslms results`	`-c`, `-a`
Calendar/deadlines	`canvaslms calendar`	`-c`, date range flags
Users/enrollment	`canvaslms users`	`-c`, role filters
Groups	`canvaslms groups`	`-c`

Regex Filtering Patterns

Course matching is case-insensitive: "dd2520" matches "DD2520"
Use anchors for precision: "^DD2520$" for exact match
Partial match works: "crypt" matches "Applied Cryptography"
Combine flags for specificity: -c "DD2520" -m "week 3" -a "lab"

Output and Caching

list commands produce tab-delimited CSV (pipe through column -t -s$'\t' for readability)
view commands produce full content (markdown, HTML, or YAML frontmatter + content)
Results are cached; use --no-cache to force a fresh fetch
Pages view output includes YAML frontmatter with metadata

Common Pitfalls

Always identify the course first:

BAD:  canvaslms assignments list -a "lab 1"     # No course specified
GOOD: canvaslms assignments list -c 12345 -a "lab 1"

Use list before view to discover item names:

BAD:  canvaslms pages view -c 12345 -p "syllabus"   # Guessing the page name
GOOD: canvaslms pages list -c 12345                   # Discover available pages
      canvaslms pages view -c 12345 -p "Course Syllabus"  # Use actual name

Use the right content type flag for discussions:

BAD:  canvaslms discussions list -c 12345              # Missing type
GOOD: canvaslms discussions list -c 12345 -t announcement
GOOD: canvaslms discussions list -c 12345 -t discussion

Scope

This skill is read-only — it retrieves and presents course information. It does not create, modify, or delete any Canvas content. To create quiz content, use the canvas-quiz skill instead.

المزيد من هذا المستودع

نفس المستودع

didactic-notes

dbosk/claude-skills

Document pedagogical design decisions in educational materials using the didactic LaTeX package and \ltnote command. Use proactively when (1) writing or editing educational LaTeX materials with pedagogical content, (2) adding or revising variation-theory annotations such as "What varies" or "What stays invariant", (3) explaining design trade-offs or choices in educational materials, (4) documenting why specific examples or exercises are sequenced in a particular way, or (5) moving pedagogical reasoning out of student-facing prose and into instructor notes. Invoke when user mentions didactic notes, \ltnote, pedagogical reasoning, learning theory notes, educational design documentation, or asks to move pedagogical reasoning to instructor notes. CRITICAL: Pedagogical reasoning (variation/invariance labels, pattern names, design rationale) should be in \ltnote{}, NOT in student-facing text.

2026-05-191

latex-writing

dbosk/claude-skills

Guide LaTeX document authoring following best practices and proper semantic markup. Use proactively when: (1) writing or editing .tex files, (2) writing or editing .nw literate programming files, (3) literate-programming skill is active and working with .nw files, (4) user mentions LaTeX, BibTeX, or document formatting, (5) reviewing LaTeX code quality. Ensures proper use of semantic environments (description vs itemize), csquotes (\enquote{} not ``...''), and cleveref (\cref{} not \S\ref{}).

2026-05-191

variation-theory

dbosk/claude-skills

Apply variation theory of learning to structure content using contrast, generalization, and fusion patterns. Variation must target the critical aspects of the learning objective. Use proactively when (1) writing educational materials, explanations, tutorials, or lecture slides, (2) designing or reviewing examples in documentation, READMEs, or literate programs (.nw files), especially when multiple examples illustrate alternative approaches to the same task, (3) structuring code examples, CLI usage examples, or API examples where the reader should notice what differs between alternatives, (4) user mentions variation theory, learning theory, pedagogy, contrast, invariance, or critical aspects. Also activate when asked to elaborate, make concrete, or add examples to existing content. Works alongside literate-programming and didactic-notes skills; in educational LaTeX or .nw materials, keep variation-analysis labels in \ltnote{} rather than student-facing prose.

2026-05-191

literate-programming

dbosk/claude-skills

CRITICAL: ALWAYS activate this skill BEFORE making ANY changes to .nw files. Use proactively when: (1) creating, editing, reviewing, or improving any .nw file, (2) planning to add/modify functionality in files with .nw extension, (3) user asks about literate quality, (4) user mentions noweb, literate programming, tangling, or weaving, (5) working in directories containing .nw files, (6) creating new modules/files that will be .nw format. Trigger phrases: 'create module', 'add feature', 'update', 'modify', 'fix' + any .nw file. Never edit .nw files directly without first activating this skill to ensure literate programming principles are applied. (project, gitignored)

2026-05-191

document-issues

dbosk/claude-skills

Captures unrelated follow-up issues discovered during repository work and records them for later. Use proactively when: (1) working inside a git repository, (2) an out-of-scope bug, cleanup item, missing test or documentation, or tech-debt task is discovered, (3) the user mentions filing an issue, follow-up, backlog item, or nytid import. Prefer gh issue, ask before creating anything unless autonomous issue capture is enabled, and optionally import created GitHub issues into nytid todo.

2026-04-171

canvas-quiz

dbosk/claude-skills

Write and review Canvas LMS quiz JSON files (INL1Quiz-*.json) for the tilkry cryptography course. Use proactively when: (1) creating, editing, or reviewing INL1Quiz JSON files, (2) user asks to write quiz questions for a lecture topic, (3) user asks to review quiz quality, redundancy, or distractor balance, (4) user mentions Canvas quiz, INL1Quiz, quiz JSON, or quiz questions. Covers JSON structure, question design, scoring, redundancy analysis, and validation.

2026-04-131

المصدر

dbosk

dbosk/claude-skills

فتح مستودع GitHub عرض مستودعات المنشئ

أمر التثبيت

تنزيل

تشغيل في Manus

مفيد لـSOC

مطوّرو البرمجياتمهن الحاسوب والرياضيات15-1252L4

name

canvas-info

description

Canvas Course Information Research

Overview

For detailed options on any subcommand, run canvaslms <subcommand> -h.

Research Workflow

Follow these steps when answering a Canvas-related question:

Step 1: Identify the Course

canvaslms courses              # List all courses
canvaslms courses "regex"      # Filter by name/code (case-insensitive regex)

Note the course ID from the output. Use it with -c <id> in subsequent commands.

Step 2: Explore Course Structure

Choose the right entry point based on the question:

Question type	Start with
"What's in this course?"	`canvaslms modules list -c <id>`
"What assignments exist?"	`canvaslms assignments list -c <id>`
"Any announcements?"	`canvaslms discussions list -c <id> -t announcement`
"What pages are available?"	`canvaslms pages list -c <id>`
"What are the deadlines?"	`canvaslms calendar -c <id>`
"How did students do?"	`canvaslms results -c <id>`

Step 3: Drill into Content

Use view subcommands to read specific items:

canvaslms modules view -c <id> -m "module regex"
canvaslms pages view -c <id> -p "page regex"
canvaslms assignments view -c <id> -a "assignment regex"
canvaslms discussions view -c <id> -d "discussion regex"

The view commands output full content (markdown for pages, HTML for assignments). The list commands output tab-delimited CSV summaries.

Step 4: Refine with Filters

Most commands accept regex filters and additional flags. Run canvaslms <subcommand> -h to discover available filters for each command.

Common refinement patterns:

Combine course + item filters: -c "DD2520" -a "lab"
Filter by module: -c <id> -m "week 3"
Filter submissions by user: canvaslms submissions -c <id> -u "username"

Step 5: Synthesize and Answer

After gathering data:

Quote relevant content directly when answering
Summarize lists into readable format (tables, bullets)
If data seems stale, suggest re-running with --no-cache
Provide the course/assignment/page names so the user can navigate in Canvas

Quick Reference

To find...	Command	Key flags
All courses	`canvaslms courses`	regex filter, `-i` for ID only
Course modules	`canvaslms modules list`	`-c`, `-m`
Module contents	`canvaslms modules view`	`-c`, `-m`
Assignments	`canvaslms assignments list`	`-c`, `-a`, `-m`
Assignment details	`canvaslms assignments view`	`-c`, `-a`
Wiki pages	`canvaslms pages list`	`-c`, `-p`, `-m`
Page content	`canvaslms pages view`	`-c`, `-p`
Announcements	`canvaslms discussions list`	`-c`, `-t announcement`
Discussions	`canvaslms discussions list`	`-c`, `-t discussion`
Discussion content	`canvaslms discussions view`	`-c`, `-d`
Quizzes	`canvaslms quizzes list`	`-c`, `-q`
Submissions	`canvaslms submissions`	`-c`, `-a`, `-u`
Grades/results	`canvaslms results`	`-c`, `-a`
Calendar/deadlines	`canvaslms calendar`	`-c`, date range flags
Users/enrollment	`canvaslms users`	`-c`, role filters
Groups	`canvaslms groups`	`-c`

Regex Filtering Patterns

Course matching is case-insensitive: "dd2520" matches "DD2520"
Use anchors for precision: "^DD2520$" for exact match
Partial match works: "crypt" matches "Applied Cryptography"
Combine flags for specificity: -c "DD2520" -m "week 3" -a "lab"

Output and Caching

list commands produce tab-delimited CSV (pipe through column -t -s$'\t' for readability)
view commands produce full content (markdown, HTML, or YAML frontmatter + content)
Results are cached; use --no-cache to force a fresh fetch
Pages view output includes YAML frontmatter with metadata

Common Pitfalls

Always identify the course first:

BAD:  canvaslms assignments list -a "lab 1"     # No course specified
GOOD: canvaslms assignments list -c 12345 -a "lab 1"

Use list before view to discover item names:

BAD:  canvaslms pages view -c 12345 -p "syllabus"   # Guessing the page name
GOOD: canvaslms pages list -c 12345                   # Discover available pages
      canvaslms pages view -c 12345 -p "Course Syllabus"  # Use actual name

Use the right content type flag for discussions:

BAD:  canvaslms discussions list -c 12345              # Missing type
GOOD: canvaslms discussions list -c 12345 -t announcement
GOOD: canvaslms discussions list -c 12345 -t discussion

Scope

This skill is read-only — it retrieves and presents course information. It does not create, modify, or delete any Canvas content. To create quiz content, use the canvas-quiz skill instead.