agentsclimarketplace
Sign in

Er diagram

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

Draw an entity-relationship / data-model diagram in the open tldraw offline canvas — entities with their key attributes, connected by relationship edges with cardinality. Use when the user asks for an ER diagram, a data model, a database schema diagram, or to show how tables/entities relate. Produces the same entity-card layout and cardinality 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 er-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, 416 tokens by cl100k_base, as published. Nobody here has run it

er-diagram

Consistent entity-relationship diagrams from a schema description.

Before you start

  • Read references/shared/bridge.md (bundled with this skill), references/shared/style.md, references/shared/diagramming.md.
  • Read ./reference.md — entity-card format and cardinality notation.

Target document

Convention: ~/canvas/diagrams/<model>-er.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, a table list, or a schema/DDL snippet. Normalize to { entities:[{key,name,attrs:[{name,type,pk?,fk?}]}], relationships:[{from,to,label,card:'1-1'|'1-N'|'N-N'}] }.

Workflow

  1. Parse → normalized model. Keep attributes concise (name + type; mark PK/FK).
  2. Render each entity as a card: a title box (entity name, colored blue) with a text block of attributes beneath it (PK first, FK marked). Grid layout per reference.md.
  3. Connect related entities with bound arrows; label with cardinality. For N-N note the join entity if one exists.
  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 one card per entity; getBindings() confirms relationship edges are bound; getLints() clean.

Report

Doc id/name, entity count, relationship count, lint status.

What ships with it: 10 files

78.3 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.