sg-draft
Draft full slide content (titles, bullets, speaker notes, graphics descriptions) from an outline
What this skill does
# Slide Generator: Draft Step Draft full slide content from an outline. Uses structured single-call generation (one API call per slide) with batching (groups of 4) for efficiency. Produces a complete presentation markdown with titles, bullets, speaker notes, and graphics descriptions. ## Pre-loaded Context **Working directory:** !`pwd` **Available outline files:** !`ls -la outline*.json 2>/dev/null || echo "No outline files found"` ## Proactive Triggers Suggest this skill when: 1. User has an outline and wants to generate full slide content 2. User says "draft the slides" or "write the content" 3. User completed the outline step and wants to continue 4. User wants to go from structure to full presentation content ## Prerequisites - `slide-generator` package installed - `ANTHROPIC_API_KEY` set in environment - An `outline.json` file from the outline step ## Input Validation **Required:** - `<outline.json>` - Path to outline file **Optional:** - `--output <path>` - Output file path (default: `presentation.md`) - `--tone <tone>` - Content tone: professional, casual, academic, technical (default: professional) - `--audience <audience>` - Target audience description ## Instructions 1. **Verify input**: Confirm the outline JSON file exists and is valid 2. **Run draft generation**: ```bash sg draft outline.json --output presentation.md ``` 3. **Verify output**: Confirm `presentation.md` was created with full slide content 4. **Report results**: Show slide count, total word count, and a sample slide ## How It Works The draft step uses: - **Structured single-call**: Each slide generated in one API call (not 4 separate calls) - **Batch generation**: Slides grouped in batches of 4 for efficiency - **Inter-slide context**: Rolling 5-slide context window for coherence - **Temperature 0.5**: Balanced creativity for content generation - **Research cache**: Reuses research findings for factual accuracy ## Error Handling | Error | Cause | Fix | |-------|-------|-----| | `File not found` | Wrong path to outline.json | Check file path | | `Rate limit` | Too many API calls in batch | Wait and retry (built-in backoff handles this) | | `Content too short` | Outline lacks detail | Re-run outline with more target slides | ## Output The draft step produces `presentation.md` containing: - Full markdown-formatted slides - Titles, bullet points, and detailed speaker notes - Graphics descriptions for each slide (feeds image generation) - Proper frontmatter with metadata ## Next Step After draft completes, run the optimize step: ```bash sg optimize presentation.md ``` Or use `/sg-optimize` to continue the pipeline.
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.