agentsclimarketplace
Sign in

Flowchart

Skill prateek11rai/tldraw-canvas-kit/skills/flowchart

Draw a process or decision flowchart in the open tldraw offline canvas — start/end terminals, process steps, and decision branches connected with bound arrows. Use when the user asks for a flowchart, a process flow, a decision tree, or an algorithm/workflow diagram. Produces the same top-to-bottom layout and shape vocabulary 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 flowchart

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.1 KB, 396 tokens by cl100k_base, as published. Nobody here has run it

flowchart

Consistent process/decision flowcharts from a step description.

Before you start

  • Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/diagramming.md.
  • Read ./reference.md — shape vocabulary and layout.

Target document

Convention: ~/canvas/diagrams/<process>-flow.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 steps or a numbered list. Normalize to { nodes:[{key,label,kind:'start'|'end'|'process'|'decision'}], edges:[{from,to,label}] }. Decision nodes have labeled out-edges (typically yes/no).

Workflow

  1. Parse → normalized model.
  2. Lay out top→bottom (see reference.md): terminals as ellipses, processes as rectangles, decisions as diamonds; branches fan left/right below a decision.
  3. Connect with bound arrows; label decision branches. Color yes→green, no→red only at decisions (per style.md); otherwise default.
  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 the right node kinds; getBindings() confirms bound edges; getLints() clean.

Report

Doc id/name, node count, decision count, lint status.

What ships with it: 10 files

77.8 KB alongside SKILL.md, 2 of them executable

assets/

references/

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.