send-to-pages

Copy selected HTML, CSS, JS, themes, and assets from OUTPUTS to a GitHub Pages target folder.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/julieclarkson/case-study-maker --skill send-to-pages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send-to-pages
Source: https://github.com/julieclarkson/case-study-maker/tree/main/skills/send-to-pages
Command: npx skills add https://github.com/julieclarkson/case-study-maker --skill send-to-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a safe, selective way to publish generated HTML outputs and their dependencies to a GitHub Pages-style folder or another repo without manually hunting files, preserving themes and assets needed for proper rendering.

Core Features & Use Cases

  • Selective publishing: Detects output types from filenames and copies only the outputs the developer chooses (e.g., portfolio, marketing, pitch-deck).
  • Dependency preservation: Copies matching CSS, JS, theme files, and portfolio assets so pages render correctly after deployment.
  • Config integration: Reads and optionally updates .case-study/config.json to persist the target pagesPath or pagesRepo.
  • Use Case: Move the latest portfolio and marketing HTML plus their styles and assets into docs/ so the repo's GitHub Pages serves an up-to-date portfolio.

Quick Start

Ask the plugin to copy the selected outputs from OUTPUTS to your target pages folder, for example instruct it to send portfolio and marketing outputs to docs.

Frequently Asked Questions about send-to-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I copy generated HTML portfolio outputs to a GitHub Pages folder?

To copy generated HTML portfolio outputs to a GitHub Pages folder, this Skill parses filenames from your OUTPUTS directory and selectively moves the chosen HTML, CSS, JS, themes, and assets into the target path specified in your configuration.

What is the best way to publish static site assets to GitHub Pages from an OUTPUTS directory?

Publishing static site assets to GitHub Pages from an OUTPUTS directory is done by reading the target pages path or repo from .case-study/config.json and copying the detected output types along with their referenced dependencies for proper rendering.

Does this file-copy automation preserve CSS and JS dependencies when deploying to GitHub Pages?

Yes, this file-copy automation preserves CSS and JS dependencies by detecting output types from filenames and copying the matching themes, styles, and assets needed so the published pages render correctly without manual file hunting.

Can I use this deployment tool to send pitch-deck outputs to a specific pages repo?

Yes, you can send pitch-deck outputs to a specific pages repo by ensuring the OUTPUTS directory exists and configuring the pagesRepo value in your .case-study/config.json file to point to the target repository.

Do I need a config.json file to automate file copying to a local GitHub Pages path?

Yes, you need a .case-study/config.json file to define the pagesPath or pagesRepo target so the automation can read the destination and persist the configuration for copying your generated HTML, CSS, and JS files.

Why does my portfolio deployment to GitHub Pages break styling and asset links?

Portfolio deployment to GitHub Pages may break styling if the file-copy process does not preserve the required CSS, JS, and theme assets, which this Skill solves by selectively copying all referenced dependencies alongside the HTML.