$npx -y skills add ShZhao27208/Aut_Sci_Write --skill sci-htmlGenerate academic presentation-style HTML slide decks and browser reports from PDFs, structured text, Markdown, paper summaries, outlines, or research notes. Use whenever the user wants to convert a scientific paper PDF directly into an interactive HTML report, clickable web pres
| 1 | # Sci HTML |
| 2 | |
| 3 | Use this skill to create browser-based academic slide decks inside the Aut_Sci_Write suite. It can work from prepared Markdown/JSON, or run the full paper workflow from PDF to structured insights, extracted figures, and HTML deck. |
| 4 | |
| 5 | Use `sci-html` for shareable browser output. Use `sci-ppt` when the user needs a real `.pptx`. Use `sci-extract` when the user only wants a text analysis without a presentation artifact. |
| 6 | |
| 7 | ## When To Use |
| 8 | |
| 9 | Use this skill when the user asks for HTML slides, clickable presentation webpages, browser-based academic presentations, Markdown to slide deck, paper summary to web presentation, PDF paper to HTML report, or a PPT-like HTML file with left/right navigation. |
| 10 | |
| 11 | ## Output |
| 12 | |
| 13 | Always create a deck directory containing `index.html`, `deck.json`, `assets/style.css`, `assets/deck.js`, and copied local figures under `assets/figures/`. |
| 14 | |
| 15 | Do not create single-file HTML. Directory output is the standard mode because it keeps the presentation maintainable and avoids oversized embedded assets. |
| 16 | |
| 17 | ## Workflow |
| 18 | |
| 19 | 1. Parse the user's source content into a deck model. |
| 20 | 2. Add cover, table of contents, section, summary, and ending slides when appropriate. |
| 21 | 3. Validate image paths and slide structure. |
| 22 | 4. Render HTML, CSS, and JS. |
| 23 | 5. Tell the user the output path and navigation controls. |
| 24 | |
| 25 | ## PDF Paper Workflow |
| 26 | |
| 27 | For a source PDF, use the integrated `paper` command rather than requiring separate `sci-extract` or `sci-figure` skills: |
| 28 | |
| 29 | ```bash |
| 30 | python scripts/generate_html_deck.py paper paper.pdf -o out/paper-report --author "Presenter" |
| 31 | ``` |
| 32 | |
| 33 | When working from the Aut_Sci_Write repository root, run: |
| 34 | |
| 35 | ```bash |
| 36 | python skills/sci-html/scripts/generate_html_deck.py paper paper.pdf -o skills/sci-html/out/paper-report --author "Presenter" |
| 37 | ``` |
| 38 | |
| 39 | This writes `structured_insights.json`, `figure_manifest.json`, extracted files under `figures/`, a generated `{paper-stem}-deck.md`, and the final `index.html`. |
| 40 | |
| 41 | The PDF workflow uses bundled integrations copied from `sci-extract` and `sci-figure`. It requires `PyMuPDF`, `pdfplumber`, `numpy`, `opencv-python`, `Pillow`, and `pytesseract`; Tesseract OCR is optional and only affects subfigure OCR. |
| 42 | |
| 43 | The integrated `sci-extract` logic detects original research versus review literature. Original research decks emphasize problem, method, results, innovation, applications, and limits. Review, survey, systematic review, scoping review, and meta-analysis decks emphasize scope, taxonomy, evidence base, consensus, controversies, evidence quality, research gaps, future directions, and important figures or tables. Use `--paper-type auto|research|review` when the user wants to override automatic routing. |
| 44 | |
| 45 | ## Presentation Markup |
| 46 | |
| 47 | - Put `layout: section` at the top of a Markdown slide block to create a chapter divider. |
| 48 | - Put `subtitle: 01` below `layout: section` to show the chapter number. |
| 49 | - Use `**key phrase**` or `==key phrase==` for red emphasis. |
| 50 | - Keep bullets concise; generated bullet slides use numbered key-point cards by default. |
| 51 | - When a slide has only one or two content bullets, render it as plain statements without visible item numbers. |
| 52 | - Long slide and paper titles are automatically fitted by shrinking the heading and expanding its line width so the title stays on the page. |
| 53 | - Sparse slides automatically receive subtle topic motifs from title and bullet keywords, so visually empty areas are filled without requiring extra image assets. |
| 54 | |
| 55 | ## Navigation Controls |
| 56 | |
| 57 | Generated decks support mouse click, left-third click for previous slide, explicit Prev/Next buttons, left/right arrow keys, space, Home/End, F fullscreen, and URL hash state such as `#/3`. |
| 58 | |
| 59 | ## Design Rules |
| 60 | |
| 61 | Keep slides academic, readable, and presentation-oriented. Avoid long paragraphs. Prefer figures, concise numbered points, section breaks, and strong hierarchy. Use decorative but unobtrusive visual patterns to reduce empty space. Keep section and ending slides centered. Escape |