improve

Manages a git-tracked markdown kanban board for course improvement cards.

4|4|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/chaz-clark/canvas-toolbox --skill improve-chaz-clark
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve
Source: https://github.com/chaz-clark/canvas-toolbox/tree/main/.agents/skills/improve
Command: npx skills add https://github.com/chaz-clark/canvas-toolbox --skill improve-chaz-clark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Course improvement ideas from audits, teaching sessions, and handoffs get lost in chat history or one-off notes. This Skill keeps them in one local, git-tracked kanban board (IMPROVEMENTS.md) so every improvement is tracked to done instead of rediscovered each term. ## Core Features & Use Cases - Card Logging: Turn audit findings, instructor notes, and handoff action items into kanban cards with stable IDs, source, size, and risk tags. - Lifecycle Management: Move cards through Backlog, Ready, In Progress, In Review, and Done columns with a WIP limit and an instructor review gate. - Use Case: After a course audit surfaces five findings, ask the agent to turn them into cards on the board, prioritize the Ready column, and pull the top card into In Progress. ## Quick Start Ask the agent to log this improvement idea to the board and show what is next in the Ready column.

Frequently Asked Questions about improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track course improvement ideas across teaching terms?▼

Log each idea as a card in IMPROVEMENTS.md, a git-tracked markdown kanban board at the course root. Cards carry a stable ID, source, size, and risk, and move from Backlog through Done so nothing is lost between sessions.

How to turn course audit findings into actionable tasks?▼

Write each audit finding as a card on the improvement board with src tagged as the audit date. Prioritize them in the Ready column, then pull the top card into In Progress when work begins.

Does the improvement board require an external service or account?▼

No external service is required. The board is a plain markdown file stored in the course repository, so it travels with git and the instructor can edit it directly.

Can cards be marked Done automatically after work finishes?▼

No. Finished work lands in the In Review column until the instructor verifies it. Nothing self-marks Done, and closing a card requires the PR or commit link and the date.

Is the improvement board safe to commit with student data policies?▼

Yes. The board contains only course context with no student PII, classified as Zone-1 content that is safe to read and commit to the repository.