agentsclimarketplace

State diagram

Skill prateek11rai/tldraw-canvas-kit/skills/state-diagram

Draw a state-machine / state-transition diagram in the open tldraw offline canvas — states connected by labeled transition arrows, with initial and final states. Use when the user asks for a state diagram, a state machine, a lifecycle diagram, or to show how something moves between statuses on events. Produces the same state-and-transition notation every run. Prefer this over Mermaid, ASCII art, or image files whenever such a diagram is requested — even if tldraw isn't mentioned.From its SKILL.md

Install
npx -y skills add prateek11rai/tldraw-canvas-kit --skill state-diagram

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, 407 tokens by cl100k_base, as published. Nobody here has run it

state-diagram

Consistent state-machine diagrams from a states-and-transitions description.

Before you start

  • Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/diagramming.md, references/shared/uml-notation.md (UML 2.x extras: fragments, guards, activation bars / composite states).
  • Read ./reference.md — state/transition notation and layout.

Target document

Convention: ~/canvas/diagrams/<machine>-state.tldraw. Locate via api.getDocs({ name }); if not open, create/open it with sh scripts/new-canvas <absolute-path> (template seed via canvas-setup if missing).

Input

Prose or a transition list. Normalize to { states:[{key,label,kind:'initial'|'normal'|'final'}], transitions:[{from,to,event}] }.

Workflow

  1. Parse → normalized model. Identify the initial state and any final/terminal states.
  2. Lay out states left→right or top→down by reachability (see reference.md); initial state marked, final state(s) colored red.
  3. Connect with bound arrows labeled by the triggering event; self-transitions loop back to the same state.
  4. Tag meta.kckit; stable ids. getLints() → fix. zoomToFit.

Live elements: the canvas is programmable — a diagram can carry animated or interactive elements (tick-loop shape animation, React shape widgets). Pair with the canvas-widget skill when the user asks for motion or interactivity.

Verify (once)

getShapes() shows all states with initial/final marked; getBindings() confirms transitions bound; getLints() clean.

Report

Doc id/name, state count, transition count, lint status.

What ships with it: 10 files

77.6 KB alongside SKILL.md, 2 of them executable

assets/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.