sg-build
Assemble final PowerPoint (.pptx) from presentation markdown and generated images
What this skill does
# Slide Generator: Build Step Assemble the final PowerPoint file (.pptx) from the presentation markdown and generated images. Uses python-pptx to create a professional slide deck with the selected template. ## Pre-loaded Context **Working directory:** !`pwd` **Available presentation files:** !`ls -la *.md 2>/dev/null | grep -i pres || echo "No presentation files found"` **Available images:** !`ls images/ 2>/dev/null | wc -l || echo "0"` **Available templates:** !`sg list-templates 2>&1 || echo "Cannot list templates"` ## Proactive Triggers Suggest this skill when: 1. User wants to create the final PowerPoint file 2. User says "build", "create the pptx", "assemble the deck", or "generate PowerPoint" 3. User completed image generation and wants the final output 4. User has a presentation.md and wants to skip to building ## Prerequisites - `slide-generator` package installed - A `presentation.md` file with slide content - Generated images in `images/` directory (optional — builds without images if missing) ## Input Validation **Required:** - `<presentation.md>` - Path to presentation markdown file **Optional:** - `--template <name>` - Template to use (default: `generic`). Use `sg list-templates` to see options - `--style <path>` - Custom style JSON file for colors, fonts, sizing - `--output <path>` - Output .pptx file path ## Instructions 1. **Verify input**: Confirm presentation markdown and images exist 2. **List templates** (if user hasn't specified): ```bash sg list-templates ``` 3. **Run build**: ```bash sg build presentation.md --template generic ``` 4. **Verify output**: Confirm .pptx file was created 5. **Report results**: Show file path, file size, slide count ## How It Works The build step: - Parses markdown into structured slide data (titles, bullets, notes, image refs) - Classifies each slide type (title, content, two-column, image-heavy, etc.) - Applies template layout rules for each slide type - Embeds generated images at appropriate positions - Adds speaker notes, slide numbers, and footers - Uses dynamic year detection for copyright footers ## Error Handling | Error | Cause | Fix | |-------|-------|-----| | `Template not found` | Invalid template name | Run `sg list-templates` | | `No slides parsed` | Malformed markdown | Check presentation.md format | | `Image not found` | Missing image file | Re-run `sg generate-images` or use `--skip-images` | | `python-pptx error` | Template corruption | Try a different template | ## Output The build step produces: - A `.pptx` PowerPoint file ready for presentation - File is named based on the topic or output flag ## Custom Templates Install custom templates to `~/.slide-generator/templates/<name>/`: - Must contain a `.pptx` template file - Optional `template.py` extending `PresentationTemplate` - Optional `style.json` for color/font configuration
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.