agentleFS
ai-workspace-labai-workspace-lab/xworkspace-core-skills/skills/workflows/research-to-slide-deck/SKILL.md

research-to-slide-deck

Skill8 starsChanged 5 months agoMITView on GitHub

研究到幻灯片工作流:将研究资料、来源和主题 brief 转成可验证的演示文稿。Workflow skill for turning research notes, sources, or a topic brief into a verified slide deck; use for PPT, PPTX, slides, research presentations, briefing decks, or source-backed presentations.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a PPTX writer is unavailable, produce a PDF deck and state that format clearly.

    line 20
  2. Very specific:

    Write deck-outline.md before creating slides.

    line 38
  3. Distinctive:

    Do not begin slide generation until the outline is coherent.

    line 48
  4. Distinctive:

    Create the deck from the outline:

    line 52
  5. Distinctive:

    Use charts, tables, diagrams, or screenshots only when they support the message.

    line 60
  6. Very specific:

    check that source-backed claims map to research/sources.md

    line 71
  7. Distinctive:

    check text does not overflow obvious slide containers

    line 72
  8. Distinctive:

    If verification cannot run, report the missing verifier and keep the generated deck plus source files.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Research To Slide Deck Workflow

This workflow converts research into a presentation with explicit source, outline, slide, and verification phases.

Output Contract

Final deliverables must stay inside the current task artifact scope:

  • research/sources.md
  • deck-outline.md
  • slides/slide-notes.md
  • exports/deck.pptx or exports/deck.pdf
  • DELIVERY.md

When a PPTX writer is unavailable, produce a PDF deck and state that format clearly.

Phase 1: Research

Gather or parse source material into research/sources.md.

Each source note should capture:

  • title
  • URL or local path when available
  • date if relevant
  • key facts
  • how it supports the deck

For current facts, live sources, pricing, market data, product specs, or recent events, verify against live sources before writing the deck.

Phase 2: Deck Outline

Write deck-outline.md before creating slides.

The outline must include:

  • audience and purpose
  • 6-12 slide titles unless the user specifies otherwise
  • one message per slide
  • required charts, screenshots, tables, or diagrams
  • source mapping per slide

Do not begin slide generation until the outline is coherent.

Phase 3: Slide Production

Create the deck from the outline:

  • title slide
  • agenda or context slide when useful
  • evidence slides with concise headings
  • visual slides for comparisons, timelines, architecture, or workflow
  • closing recommendation or next steps

Use charts, tables, diagrams, or screenshots only when they support the message. Avoid decorative filler.

When creating or repainting slide illustrations, read ../../marketplace/pptx/editable-reconstruction.md only for its image provider order. Generate the illustration that best fits the slide; do not force a text-free background or separate editable text layer for normal artwork. Apply the complete one-background-image-plus-editable-text workflow only when the user explicitly requests editable reconstruction of flattened source pages.

Phase 4: Verification

Before final response:

  • confirm exports/ contains the final deck
  • render or inspect the deck when tooling is available
  • check slide count
  • check that source-backed claims map to research/sources.md
  • check text does not overflow obvious slide containers

If verification cannot run, report the missing verifier and keep the generated deck plus source files.

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.