conference-talk-builder
Create conference talk outlines and iA Presenter markdown slides using the Story Circle narrative framework. Use when the user wants to structure a tech talk, create presentation slides, or needs help organizing talk ideas into a story-driven format.
What this skill does
# Conference Talk Builder This skill helps create compelling conference talk outlines and iA Presenter markdown slides using the Story Circle narrative framework. ## Process Follow these steps in order when building a conference talk: ### 1. Gather Information Ask the user for: - Talk title and topic - Target audience and their expected knowledge level - Main points they want to cover - Brain dump of everything they know about the topic - Problem they're solving or story they're telling - Any constraints (time limit, specific technologies, etc.) ### 2. Read the Story Circle Framework Load `references/story-circle.md` to understand the eight-step narrative structure. The framework maps tech talks to: - Top half: Established practices and order - Bottom half: Disruption and experimentation ### 3. Create the Outline Structure the talk using the eight Story Circle steps: 1. Introduction - Current status quo 2. Problem Statement - What needs solving 3. Exploration - Initial attempts 4. Experimentation - Deep investigation 5. Solution - The breakthrough 6. Challenges - Implementation difficulties 7. Apply Knowledge - Integration into project 8. Results & Insights - Lessons learned Map the user's content to these steps. Show this outline to the user and refine based on feedback. ### 4. Generate iA Presenter Slides Read `references/ia-presenter-syntax.md` for markdown formatting rules. Create slides that: - Use `---` to separate slides - Add tabs (`⇥`) before content that should be visible on slides - Leave speaker notes without tabs (spoken text only) - Include comments with `//` for reminders - Format code blocks with proper syntax highlighting - Keep slides focused on one concept each Structure the slide deck: - Title slide - Introduction slide with your photo/bio - One or more slides per Story Circle step - Code examples broken across multiple slides for readability - Closing slide with contact info and resources ### 5. Refine and Iterate After showing the slides: - Ask if sections need expansion or compression - Check if code examples need better formatting - Verify the story flow makes sense - Adjust based on user feedback ## Key Principles **Tell a Story**: You don't need to be an expert. Focus on how you approached a problem and solved it. **Keep It Readable**: Break code across slides. Use syntax highlighting. Test on bad projectors (consider light themes). **Engage the Audience**: Use humor where appropriate. Ask questions. Make eye contact. **Make Follow-up Easy**: Include a memorable URL or QR code on the final slide linking to resources. ## Bundled Resources ### References - `references/story-circle.md` - Eight-step Story Circle framework with examples. Read this first to understand the narrative structure. - `references/ia-presenter-syntax.md` - Complete iA Presenter markdown syntax reference. Read this when generating slides. ## Example Workflow User: "I want to create a talk about migrating from JavaScript to TypeScript" 1. Gather their experience, main points, and target audience 2. Read `story-circle.md` 3. Map their content: - Introduction: Current JS codebase - Problem: Type safety issues and bugs - Exploration: Research into TypeScript - Experimentation: Pilot conversion on one module - Solution: Incremental migration strategy - Challenges: Third-party library types - Apply Knowledge: Full codebase migration - Results: 40% reduction in runtime errors 4. Read `ia-presenter-syntax.md` 5. Generate markdown slides with proper formatting 6. Iterate based on feedback
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.