Publish To Pages

Publish to Pages

Convert a local presentation, PDF, HTML file, or Google Slides URL into index.html, publish it with the bundled scripts, and report the GitHub repository URL plus the GitHub Pages URL.

When to invoke

• "Publish this PPTX to GitHub Pages."
• "Turn this PDF into a public Pages site."
• "Deploy this HTML file and give me a live URL."
• "Share this Google Slides deck through GitHub Pages."
• "Create a GitHub Pages repo for this presentation."

Prerequisites and context

Run prerequisite checks quietly and surface only failures:

command -v gh >/dev/null || echo "MISSING: gh CLI — install from https://cli.github.com"
gh auth status &>/dev/null || echo "MISSING: gh not authenticated — run 'gh auth login'"
command -v python3 >/dev/null || echo "MISSING: python3 (needed for PPTX conversion)"

poppler-utils is optional and required only for PDF rendering through pdftoppm. On Debian/Ubuntu install it with apt install poppler-utils; on macOS use brew install poppler.

Input detection

Ask for a repository name when the user did not provide one. Default to the filename without extension. Use public visibility unless the user explicitly requests private; note that GitHub Pages on private repositories requires a Pro, Team, or Enterprise plan.

Conversion commands

Use a project-local scratch path when possible. The legacy examples below use /tmp/output.html; keep the generated HTML and any assets/ directory in the same parent directory before publishing.

If python-pptx is missing, tell the user to run pip install python-pptx. If Google Slides download fails, the deck may not be publicly accessible; ask the user to make it viewable or download the PPTX manually.

Large file and asset rules

External assets mode keeps individual files below GitHub's 100MB limit. The output HTML references files in assets/, and scripts/publish.sh automatically copies the sibling assets/ directory.

Publishing procedure

1. Convert the input to an index.html-compatible file.
2. Confirm the HTML file and any sibling assets/ directory are in the same parent directory.
3. Run the bundled publisher:

bash SKILL_DIR/scripts/publish.sh /path/to/index.html REPO_NAME public "Description"

Pass private instead of public only when the user requests a private repository. The script creates the repository, pushes index.html plus assets/ when present, and enables GitHub Pages.

Troubleshooting

Progressive disclosure and bundled resources

• scripts/convert-pptx.py: converts PPTX input to slide HTML, with optional external assets.
• scripts/convert-pdf.py: renders PDF pages to navigable HTML, using Poppler when available.
• scripts/publish.sh: creates or updates the GitHub repository, pushes files, and enables Pages.

Private repositories use --private; public repositories remain the default.

Output template

## GitHub Pages publish result

**Status:** published | blocked
**Repository:** `https://github.com/USERNAME/REPO_NAME`
**Live URL:** `https://USERNAME.github.io/REPO_NAME/`

### Source
- Input: `<INPUT_FILE or Google Slides URL>`
- Conversion: `html | pptx | pdf | google-slides`
- Assets mode: `self-contained | external assets`

### Validation
- `gh auth status`: `<pass/fail>`
- Conversion command: `<pass/fail/not needed>`
- Publish command: `<pass/fail>`

**Note:** GitHub Pages can take 1-2 minutes to go live.

Quality gate

• gh, gh auth status, and python3 prerequisite checks were run or explicitly blocked.
• Input type was classified as HTML, PPTX, PDF, or Google Slides.
• PRESENTATION_ID was extracted for Google Slides downloads.
• Large-file mode was selected correctly, including --external-assets or --no-external-assets when forced.
• The HTML file and any assets/ directory shared the same parent before publishing.
• Repository visibility matched the user's request: public by default, private only when requested.
• The final response included both repository and live Pages URLs.

References

• GitHub CLI