Skip to content
cccskills
FreePublished on GitHub

deck-publisher

Turn content into a responsive, presenter-friendly slide deck published at a live URL via ReportRoom. Use when the user says "make this a deck", "turn this into slides", "presentation for", or wants something to present rather than read. Not for long-form documents (use report-publisher) or polishing an existing deck (use report-designer).

The English summary is being prepared. Showing the original description.

dashaworks/report-skills
Works withPowerPoint
See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Deck Publisher

Content → a web-native slide deck: keyboard/scroll navigable, responsive, presentable from any device, at a URL — not a .pptx attachment.

Follow the shared flow in the root SKILL.md. Deck-specific craft below.

When to use

  • "Make this a deck / slides / a presentation"
  • The content will be presented (meeting, pitch, demo) rather than read
  • If the user needs a .pptx file specifically, say so and defer to a pptx tool — this skill makes live web decks

Steps

  1. Establish the setting. Presented live by the user, or sent to be clicked through alone? A presented deck carries less text per slide (the speaker is the content); a send-ahead deck must stand alone. Ask if unclear — it changes every slide.
  2. One idea per slide. Convert the source content into a slide outline first: each slide gets a full-sentence headline that states its point (a reader who only reads headlines should get the whole argument). Show the outline before authoring the deck.
  3. Data becomes visuals. Tables of more than a few cells become charts where the design system provides them; walls of bullets become 3–4 short lines max. Anything that can't be cut goes to an appendix slide.
  4. Author + lint + approval gate per the shared flow — preview is the slide outline plus any slides with numbers on them.
  5. Publish. Return the URL and mention presenter navigation (keyboard/scroll) and that view analytics are attached for send-ahead decks.

Hard rules

  • Never exceed the point-per-slide rule to save slide count — more slides beats denser slides.
  • The first slide states the ask/conclusion when the deck is persuasive (pitch, proposal); background never comes first.
  • Keep the user's numbers exact; rounding for a headline is fine only when the exact figure appears on the same slide or in the appendix.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

client-reporter

Free

Create and publish a recurring client-facing deliverable — SEO or analytics monthly, project status report, audit results — as a branded live page with view tracking. Use when the user says "client report", "monthly report for", "status update for the client", "send this to my client". Not for one-off research shares (use report-publisher) or proposals (use proposal-tracker).

The English summary is being prepared. Showing the original description.

dashaworks/report-skills12Updated Aug 6, 2026

proposal-tracker

Free

Publish a proposal, offer, or pitch as a tracked link and report back whether it's getting read (view analytics after sending). Use when the user says "send the proposal", "did they open it", "track whether they read it", "share the offer". Not for recurring client reports (use client-reporter) or general research shares (use report-publisher).

The English summary is being prepared. Showing the original description.

dashaworks/report-skills12Updated Aug 6, 2026

report-designer

Free

Polish an existing report, deck, or HTML page to the ReportRoom design bar — visual hierarchy, typography, charts, dark mode, OG/social link preview. Use when the user says "make it beautiful", "improve the design", "it looks plain", "fix the layout" about something already written or published. Not for creating content from scratch (use report-publisher or deck-publisher).

The English summary is being prepared. Showing the original description.

dashaworks/report-skills12Updated Aug 6, 2026

report-publisher

Free

Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).

The English summary is being prepared. Showing the original description.

dashaworks/report-skills12Updated Aug 6, 2026

report-skills

Free

Shared setup and rules for the report-skills bundle (report-publisher, client-reporter, proposal-tracker, deck-publisher, report-designer). Loaded by the individual skills for the common ReportRoom MCP publish flow, account bootstrap, and safety gates. Not invoked directly — pick the specific skill for the job.

The English summary is being prepared. Showing the original description.

dashaworks/report-skills12Updated Aug 6, 2026

See all skills by dashaworks

Report a problem with this skill