agentleFS
WhatscheapWhatscheap/igly-canvas-plugin/skills/storyboard/SKILL.md

storyboard

Skill0 starsChanged 14 days agoMITView on GitHub

Lay out a storyboard or shot list for a video, ad, reel, explainer, presentation or comic as frames with scene notes on an editable Igly canvas. Use when the user plans scenes, shots, beats or slides in sequence.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use acquisition-channel-advisor, altitude-horizon-framework and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    acquisition-channel-advisor

    Evaluate and recommend customer acquisition channels based on product type, target audience, budget, and stage — covering organic, paid, referral, partnerships, and product-led growth.

    Also in 3 projects that use this

  • nandanosqlSkill

    altitude-horizon-framework

    Navigate between strategic (30,000 ft) and tactical (ground level) thinking using the Altitude-Horizon framework — knowing when to zoom in vs. out and adjusting communication to the right level.

    Also in 3 projects that use this

  • +10 more from nandanosql

The file

Files
SKILL.md

Storyboard

Frames are sketch boxes with scene descriptions, not finished pictures. Draw simple stick-figure style hints with paths only if the user asks for sketches.

1. Plan the beats

  • 4 to 12 scenes. For each: number, what we see, dialogue or voiceover, duration, camera or transition.
  • Choose the frame ratio from the format: 9:16 vertical (reels, TikTok, shorts) 270 x 480; 16:9 (YouTube, slides) 480 x 270; 1:1 (feed) 360 x 360.

2. Create

create_canvas with the project as title. Keep canvas_id.

3. Layout (one add_elements call)

  • Grid of 4 per row (3 for 16:9). Column step = frame width + 60; row step = frame height + 260.
  • Frame: rectangle at (x, y), fill: "#FFFFFF", stroke: "#1E1E1E", stroke_width: 3, corner_radius: 12, text = a short visual description centered in the frame (font_size: 20).
  • Scene number: type: "text" above the frame, bold, font_size: 26 ("1 Hook 0-3s").
  • Notes under the frame: type: "sticky", frame width x 180, color: "#FEF3C7", with voiceover/dialogue and camera direction.
  • Flow: type: "arrow" from each frame to the next frame in the same row, with from_id/to_id; label transitions ("cut", "zoom", "swipe") with label. Do not draw an arrow from the last frame of a row to the first of the next row (it cuts across the board); the scene numbers already carry the order.
  • Optional quick sketch inside a frame: one or two type: "path" strokes (e.g. a horizon line, a circle head) with stroke: "#1E1E1E".

4. Check

  • get_canvas_summary; fix spacing with arrange (align_top, distribute_horizontal with gap: 60).
  • Offer to reorder scenes (swap positions with update_elements), tighten copy to the target length, or export_png for sharing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.