2 min lesson
Canvas artifact rendered next to the chat
Complete "Canvas artifact rendered next to the chat". Check the final state against the lesson before you move on.
Check your understanding
Run this practice: Canvas — turn a dependency audit into a decision the lead can act on.
Outcome: The skill carries the layout, the query and the sort order, so next month a one-line prompt gives the team the same audit and anyone using the skill gets the same output.
Canvas — turn a dependency audit into a decision the lead can act on
Canvas artifact rendered next to the chat
SayThe lead has to decide which dependencies to bump this sprint. A markdown dump buries that — ask for it as a canvas so the decision is one glance.
Type
Audit our outdated and vulnerable dependencies and open it as a canvas: a table of package, current, latest and severity, sorted by severity.DoCursor builds the canvas and drops a card at the end of the response — open it.
SeeIt renders next to the chat as a sorted table with the high-severity count called out at the top, not a wall of terminal output. The artifact answers one question: what to upgrade first.
SayTwo rows look stale — rerun the check against the lockfile instead of hand-editing the numbers.
SeeCursor reruns the underlying query and refreshes the canvas in place; the counts now match the lockfile, and it saved the canvas so you can reopen it later without rerunning from scratch.
SayThis is a monthly job — package it as a skill so it regenerates the same shape with fresh data.
SeeThe skill carries the layout, the query and the sort order, so next month a one-line prompt gives the team the same audit and anyone using the skill gets the same output.
Learn more
Optional practice
Practice: Canvas artifact rendered next to the chat
QYou've applied it. What actually proves the work is done, not just a plausible answer?