academic-slides
Use this skill for creating or refining an academic slide deck and the talk built around it: structuring a conference talk, thesis defense, lab meeting, or paper-to-slides deck; deciding the narrative arc and slide breakdown; improving slide design and visual hierarchy; planning rehearsal, timing, Q&A, and backup slides; or generating the .pptx. Reach for it when the user is shaping the presentation itself. Do not use for writing the paper, producing standalone speaker notes/scripts/transcripts, making posters, creating isolated figures/charts outside a slide deck, or building non-academic presentations.
What this skill does
# Academic Slides A structured approach to creating academic presentation slides and preparing research talks. Covers narrative structure, slide design, visual hierarchy, delivery technique, and Q&A preparation. ## When to Use This Skill - User wants to create presentation slides for a research talk - User asks about structuring an academic presentation - User needs to prepare for a conference talk, thesis defense, or lab meeting - User wants to design a slide deck from a paper or research project - User mentions "slides", "presentation", "talk", "defense", "poster talk" --- ## Before You Start: Three Questions Before designing any slides, answer these questions clearly: 1. **What works are you presenting?** They must share a coherent research direction. If presenting multiple works, they should form a narrative arc — not a disconnected list. 2. **What problems do these works solve in that direction?** Each work should map to a specific problem. If you cannot articulate the problem in one sentence, you are not ready to present. 3. **How do you use related work to naturally introduce these problems?** Related work is not citation duty. It builds the motivation for YOUR problem. Each related work you mention should advance the audience toward understanding why your approach is needed. --- ## Core Workflow ``` Step 1: Define scope and audience Step 2: Draft narrative arc (outline) Step 3: Design slide structure (section breakdown) Step 4: Create individual slides (one idea per slide) Step 5: Add visual elements (figures, diagrams, animations) Step 6: Rehearse and time Step 7: Prepare backup / Q&A slides ``` ### Step 1: Define Scope and Audience | Audience | Adjust | |----------|--------| | Domain experts | Skip basics, go deep on method and results | | Broad CS / engineering | Explain task context, moderate technical depth | | Interdisciplinary | Start from the application, minimize jargon | | Industry | Lead with impact and demo, light on theory | **Rule of thumb**: Duration in minutes = approximate slide count. A 20-minute talk needs about 20 slides. ### Step 2: Draft Narrative Arc Use the outline template at [assets/talk-outline-template.md](assets/talk-outline-template.md) to plan your talk before making any slides. The outline forces you to articulate your key takeaway and narrative arc. ### Step 3: Design Slide Structure Break your outline into sections with claim-style headers. See [talk-structure.md](references/talk-structure.md) for two complete talk structures and section-by-section guidance. ### Step 4: Create Individual Slides One idea per slide. Follow the 10 design rules in [slide-design.md](references/slide-design.md) for visual hierarchy and layout. ### Step 5: Build the .pptx File Use [slide-creation.md](references/slide-creation.md) for practical `.pptx` creation — color palettes, layout code, charts, tables, figures, and QA workflow. ### Step 6: Rehearse and Time See [references/delivery-and-qa.md](references/delivery-and-qa.md) for the rehearsal protocol, delivery principles, and Q&A preparation. ### Step 7: Prepare Backup Slides Backup slides go after your "Thank You" slide. They are not part of the talk — they are your safety net for Q&A: - Full quantitative comparison table - Failure cases (shows honesty and preparation) - Additional ablations or analysis - Slides addressing anticipated tough questions --- ## Artifact Sources from Other Skills If you used other EvoSkills earlier in the pipeline, pull these artifacts directly: | Source Skill | Artifact | Use In Slides | |-------------|----------|---------------| | `paper-planning` | Story summary (task → challenge → insight) | Motivation slides | | `paper-planning` | Pipeline figure sketch | Method overview slide | | `paper-planning` | Experiment plan | Results structure | | `paper-writing` | Finalized figures and tables | Method + results slides | | `paper-review` | Anticipated reviewer concerns | Backup Q&A slides | See [slide-creation.md](references/slide-creation.md) for detailed layout patterns using each artifact. --- ## Counterintuitive Presentation Rules > For the 10 design rules (one idea per slide, claim-style titles, max 6 elements, etc.), see [slide-design.md](references/slide-design.md). The rules below are higher-level mindset shifts. ### 1. Your slides are not your paper A talk is an advertisement, not a lecture. Your goal is to make the audience interested enough to read the paper. Cut 80% of your paper's content. If someone can reconstruct your paper from your slides alone, your slides have too much. ### 2. Reading and listening compete Text-heavy slides force the audience to choose between reading your slides and listening to you. They will read — and stop hearing you. When you put text on a slide, you are choosing to be ignored. ### 3. Enthusiasm > polish A passionate speaker with rough slides beats a bored speaker with beautiful slides. The audience remembers your energy and clarity, not your color scheme. If you only have time to improve one thing, rehearse more — don't redesign slides. ### 4. Related work is not citation duty Use related work to BUILD your problem motivation, not to show you have read papers. Each related work slide should advance the narrative: "This approach solved X, but Y remains open — which is exactly what we address." --- ## Reference Navigation | Topic | Reference File | When to Use | |-------|---------------|-------------| | Talk structures | [talk-structure.md](references/talk-structure.md) | Organizing the narrative arc | | Slide design | [slide-design.md](references/slide-design.md) | Visual design and layout rules | | Slide creation | [slide-creation.md](references/slide-creation.md) | Building .pptx files with code | | Delivery and Q&A | [delivery-and-qa.md](references/delivery-and-qa.md) | Rehearsal, timing, Q&A preparation | | Talk outline template | [talk-outline-template.md](assets/talk-outline-template.md) | Starting a new presentation |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.