canvas-course-repo
Skill1 starsChanged 11 days agoNo licenceView on GitHub
Maintain Canvas LMS modules, pages and assignments from Markdown files in a git repository with the canvaslms CLI (the write side; canvas-info is the read side). Use proactively when: (1) creating, pushing, renaming, moving, publishing or detaching Canvas pages, assignments or module items with `canvaslms pages edit`, `assignments edit` or `modules ...`, (2) the user wants a Canvas module arranged "like that one", a module shape applied to other modules, or placeholder text headers added, (3) editing files with canvaslms front matter (`regex:`, `modules:`, `published:`) or a Makefile with push-pages targets, (4) the user mentions pushing to Canvas, module items, SubHeader, FeedbackFruits or LTI assignments in a module, (5) a Canvas-only course should get its pages and instructions as files with a Makefile to push and pull them (export, re-dating a copied round). Load BEFORE the first write: an empty file body silently replaces a description, and `modules:` in front matter is authoritative.
In this repository34 other files it gives its agents.
- canvas-quiz/CLAUDE.mdCLAUDE.md
- didactic-notes/CLAUDE.mdCLAUDE.md
- latex-writing/CLAUDE.mdCLAUDE.md
- literate-programming/CLAUDE.mdCLAUDE.md
- skill-management/CLAUDE.mdCLAUDE.md
- try-first-tell-later/CLAUDE.mdCLAUDE.md
- update-project-docs/CLAUDE.mdCLAUDE.md
- variation-theory/CLAUDE.mdCLAUDE.md
- writing-crypto/CLAUDE.mdCLAUDE.md
- backing-claimsSkill
- canvas-infoSkill
- canvas-quizSkill
- commitSkill
- didactic-decksSkill
- didactic-notesSkill
- document-issuesSkill
- inbox-infoSkill
- kth-dataSkill
- latex-writingSkill
- literate-programmingSkill
- mentipySkill
- microsoft-foundrySkill
- nytid-todoSkill
- remarkableSkill
- reviewSkill
- scientific-writingSkill
- skill-managementSkill
- stacked-prsSkill
- testingSkill
- try-first-tell-laterSkill
- update-project-docsSkill
- variation-theorySkill
- worktree-subagentsSkill
- writing-cryptoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.