agentleFS
adityareddy-devadityareddy-dev/deskstudio/skills/presentation-design/SKILL.md

presentation-design

Skill43 starsChanged 23 days agoMITView on GitHub

A slide deck on one slide system, one idea per slide, typed for a room, from an outline, a document or a one-line brief. Use for a pitch, a review, a talk or a report that will be presented.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run: Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Make a deck as the Design Manager.

Deliverable and standard. A deck to ${CLAUDE_PLUGIN_ROOT}/skills/desk/standards/deck.md: six slide types, 1920x1080, takeaway headlines, data slides to standards/chart.md, copy to standards/copy.md.

Desks.

DeskAgentTierDoes
Content Designerdesk:content-designerbuilderthe outline: one takeaway per slide, the slide type for each, speaker notes
Copy Editordesk:copy-editorseniorevery headline is a claim under twelve words, the banned list
Presentation Designerdesk:presentation-designerseniorthree slide-system roughs, then the full deck, polish rounds at the builder model
Data Viz Designerdesk:data-viz-designerbuilderevery data slide's chart as inline SVG
Image Editordesk:image-editorbuildercrops, scrims and treatment on any supplied images
Art Directordesk:art-directordirectorthe pick of the system and the notes
Creative Directordesk:creative-directordirectorsign-off

Inputs. Text (a topic or a pasted outline), a file (a Markdown doc, a plan, a report, a CSV for the data slides), a URL, a folder of images or screenshots.

Proof sizes. slide, per [data-slide].

Output under .desk/out/<id>/:

  • deck.html: every slide as <section data-slide data-type> with notes inside, per the file contract.
  • outline.md: slide number, type, headline, the one element, the note.
  • deck.pdf: Chrome print of the same file, one slide per page.
  • renders/ with one PNG per slide.

Run. Read ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md now and follow it from step 0 to step 7 as the Design Manager with the desks above. Command name for state and events: presentation-design. Changes to the loop for this command:

  • The outline comes first and is approved by the Copy Editor before any slide exists. --slides caps it (default 12 for a pitch, 20 otherwise).
  • Roughs are three slide systems, each shown on the title, one content and one data slide (three slides each) in a pattern from the standard. The pick is of the system. The full deck is then built in it.
  • Data slides' charts come from the Data Viz Designer as SVG fragments the Presentation Designer places. Proof renders every slide, and a failure names the slide number.
  • Sign-off is on the full set of renders, read as a contact sheet first, then the five slides the Art Director flags.

The ask: $ARGUMENTS

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.