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.
In this repository60 other files it gives its agents.
- animejsSkill
- sketch-animation-videoSkill
- sound-fx-for-videoSkill
- content_series_infographicSkill
- tech-article-seriesSkill
- agent-team-harnessSkill
- ai-agent-collaboration-standardSkill
- ci-cd-workflow-specSkill
- config-as-code-specSkill
- execution-ownership-migrationSkill
- feature-lane-release-workflowSkill
- generation-upgrade-acceptanceSkill
- gitops-canonical-resource-deliverySkill
- harness-workflowSkill
- infrastructure-as-code-specSkill
- issue-pr-traceability-standardSkill
- multi-environment-delivery-and-releaseSkill
- project-development-standardSkill
- store-and-startup-homepage-specSkill
- zero-trust-overlay-deliverySkill
- it-infra-continuous-pngSkill
- image-svg-pptx-proSkill
- autoglm-websearchSkill
- blogwatcherSkill
- Browser AutomationSkill
- docxSkill
- find-skillsSkill
- image-cogSkill
- image-resizerSkill
- pdfSkill
- pptxSkill
- Self-Improving Agent (With Self-Reflection)Skill
- skill-security-checkSkill
- skill-vetterSkill
- video-translatorSkill
- wan-image-video-gen-editSkill
- xlsxSkill
- backup-disaster-recovery-and-data-migrationSkill
- capacity-cost-and-resource-lifecycleSkill
- github-actions-operational-dispatchSkill
- incident-response-and-change-managementSkill
- network-dns-tls-edge-managementSkill
- observability-slo-and-alertingSkill
- secrets-identity-and-access-governanceSkill
- service-catalog-and-runbook-standardSkill
- system-db-three-role-securitySkill
- unified-observability-architectureSkill
- vault-eso-tls-certificate-governanceSkill
- ai-tech-news-videoSkill
- ai-ti-wo-shuo-explainerSkill
- it-infra-evolution-videoSkill
- it-infra-evolution-video-v2Skill
- product-intro-videoSkill
- swimlane-videoSkill
- video-understandingSkill
- ai-news-md-digestSkill
- article-to-image-seriesSkill
- content-pdf-with-imagesSkill
- evolutionary-social-copy-packSkill
- image-series-to-videoSkill
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
- Distinctive: line 20
When a PPTX writer is unavailable, produce a PDF deck and state that format clearly.
- Very specific: line 38
Write deck-outline.md before creating slides.
- Distinctive: line 48
Do not begin slide generation until the outline is coherent.
- Distinctive: line 52
Create the deck from the outline:
- Distinctive: line 60
Use charts, tables, diagrams, or screenshots only when they support the message.
- Very specific: line 71
check that source-backed claims map to research/sources.md
- Distinctive: line 72
check text does not overflow obvious slide containers
- Distinctive: line 74
If verification cannot run, report the missing verifier and keep the generated deck plus source files.
≈ “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.
Files
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.mddeck-outline.mdslides/slide-notes.mdexports/deck.pptxorexports/deck.pdfDELIVERY.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.
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
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.

