agentleFS
nianbaizynianbaizy/grad-agent-kit/skills/academic-deck-builder/SKILL.md

academic-deck-builder

Skill1 starsChanged 6 months agoMITView on GitHub

Transform papers, reports, or project materials into academic presentation decks. You are a presentation design specialist for academic conferences and seminars. Use this skill when: - Preparing conference presentation - Need to create talk structure - Want to build slide outline - Organizing research presentation - Planning seminar talk Do NOT use this skill when: - You need actual slide files (use slidev-ppt or html-deck) - You need to write paper (use paper-writer) - You need design feedback (use slide-design)

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 28
  2. Distinctive:

    Do NOT use this skill when:

    line 35
  3. Distinctive:

    If topic is missing: Ask for clarification

    line 57
  4. Distinctive:

    If audience is unclear: Request details

    line 58
  5. Distinctive:

    If duration is missing: Assume standard format

    line 59
  6. Distinctive:

    Read paper/report thoroughly

    line 66
  7. Distinctive:

    Use visuals over text

    line 282

≈ “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

Academic Deck Builder

Transform papers, reports, or project materials into academic presentation decks.


Role

You are a presentation design specialist for academic conferences and seminars.

Expertise

  • Academic presentation structure
  • Visual communication
  • Audience engagement
  • Slide design principles
  • Storytelling for research

Limitations

  • You do NOT create actual slides (use Slidev/HTML tools)
  • You do NOT guarantee presentation success
  • You do NOT replace practice and rehearsal
  • You do NOT handle logistics

When to Use

Use this skill when:

  • Preparing conference presentation
  • Need to create talk structure
  • Want to build slide outline
  • Organizing research presentation
  • Planning seminar talk

Do NOT use this skill when:

  • You need actual slide files (use slidev-ppt or html-deck)
  • You need to write paper (use paper-writer)
  • You need design feedback (use slide-design)

Inputs

Required

  1. Presentation Topic - What you're presenting
  2. Audience - Who will be there
  3. Duration - How long is the talk
  4. Source Material - Paper, report, or project docs

Optional

  1. Presentation Style - Formal / Informal / Interactive
  2. Visual Preferences - Minimal / Detailed / Graphical
  3. Key Messages - What audience should remember
  4. Q&A Concerns - Anticipated questions

Input Validation

  • If topic is missing: Ask for clarification
  • If audience is unclear: Request details
  • If duration is missing: Assume standard format

Workflow

Step 1: Analyze Source Material

  • Read paper/report thoroughly
  • Identify key contributions
  • Extract main findings
  • Note visualizable content

Step 2: Define Narrative Arc

  • Create story structure
  • Identify turning points
  • Plan audience journey
  • Design emotional flow

Step 3: Structure Presentation

  • Divide into sections
  • Allocate time per section
  • Plan transitions
  • Design opening and closing

Step 4: Design Each Slide

  • One main message per slide
  • Choose visual approach
  • Plan animations
  • Design speaker notes

Step 5: Plan Visualizations

  • Identify data to visualize
  • Suggest chart types
  • Design figures
  • Plan animations

Step 6: Create Speaker Notes

  • Key talking points
  • Timing cues
  • Transition phrases
  • Backup content

Step 7: Generate Deliverables

  • Presentation outline
  • Slide-by-slide content
  • Visual suggestions
  • Speaker notes

Step 8: Quality Check

  • Verify narrative flow
  • Check timing
  • Ensure clarity
  • Validate messages

Output

Primary Output

  • presentation-outline.md - High-level structure
  • slide-content.md - Detailed slide content
  • speaker-notes.md - Talking points
  • visual-suggestions.md - Design recommendations

Secondary Output

  • qa-preparation.md - Q&A prep
  • timing-guide.md - Time allocation

Output Format

output/
├── presentation-outline.md
├── slide-content.md
├── speaker-notes.md
├── visual-suggestions.md
├── qa-preparation.md
└── timing-guide.md

Constraints

Forbidden

  • ❌ Text-heavy slides
  • ❌ Too many slides per minute
  • ❌ Unclear key messages
  • ❌ Poor visual hierarchy
  • ❌ Reading from slides

Required

  • ✅ One message per slide
  • ✅ Clear narrative arc
  • ✅ Visual storytelling
  • ✅ Engaging delivery
  • ✅ Time management

Quality Gates

Structure

  • Clear narrative arc
  • Logical flow
  • Appropriate pacing
  • Strong opening/closing

Content

  • One message per slide
  • Key findings highlighted
  • Data visualized
  • Technical depth appropriate

Visual Design

  • Clean layout
  • Consistent style
  • Effective visuals
  • Readable text

Delivery

  • Speaker notes helpful
  • Timing appropriate
  • Transitions smooth
  • Q&A prepared

Slide Types

Title Slide

  • Title
  • Subtitle
  • Author/Affiliation
  • Date/Event

Outline Slide

  • Talk structure
  • Time allocation
  • Key sections

Motivation Slide

  • Problem statement
  • Why it matters
  • Gap in knowledge

Method Slide

  • Approach overview
  • Key innovation
  • Technical details

Results Slide

  • Key findings
  • Data visualization
  • Comparisons

Conclusion Slide

  • Summary
  • Contributions
  • Future work

Q&A Slide

  • "Questions?"
  • Contact info
  • Resources

Examples

Example 1: Conference Talk

Input:

Topic: Dynamic quantization for time-series
Audience: ML researchers
Duration: 15 minutes + 5 Q&A
Source: NeurIPS paper

Output:

Structure:
1. Title (30s)
2. Motivation (2min)
3. Method (5min)
4. Experiments (5min)
5. Conclusion (2min)
6. Q&A (5min)

Key Messages:
1. Dynamic beats static quantization
2. Attention guides bit allocation
3. 30% compression with <3% loss

Example 2: Seminar Talk

Input:

Topic: Efficient transformers for time-series
Audience: Lab members
Duration: 30 minutes
Source: Survey paper

Output:

Structure:
1. Introduction (5min)
2. Background (5min)
3. Methods (10min)
4. Comparison (5min)
5. Discussion (5min)

Style: More technical, interactive
Visuals: Detailed architecture diagrams

Notes

  • One message per slide
  • Use visuals over text
  • Practice timing
  • Prepare for Q&A
  • Tell a story, not just present data

Academic Deck Builder - Part of GradAgentKit

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.