demo-page

Convert a Markdown source document into an HTML demo page and deploy it to the gh-pages branch.

15|2|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/DirtybitGames/unityctl --skill demo-page
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demo-page
Source: https://github.com/DirtybitGames/unityctl/tree/main/.claude/skills/demo-page
Command: npx skills add https://github.com/DirtybitGames/unityctl --skill demo-page

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the rebuilding and publishing of the unityctl demo page, ensuring it accurately reflects the latest features and command outputs.

Core Features & Use Cases

  • Rebuild Demo Page: Generates an HTML version of the demo from a Markdown source.
  • Publish to GitHub Pages: Updates the live demo site hosted on GitHub Pages.
  • Use Case: When new unityctl commands are added or existing ones are updated, this Skill can be used to refresh the demo page with the latest examples and screenshots.

Quick Start

Rebuild and publish the unityctl demo page.

Frequently Asked Questions about demo-page

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

FAQPage Schema
How do I automate publishing a Markdown demo page to GitHub Pages?

To automate publishing a Markdown demo page to GitHub Pages, you can use a script that converts Markdown to HTML, copies media assets, and deploys the content to the gh-pages branch. This process rebuilds and updates the live demo site automatically.

What is the process for converting Markdown documentation into a live HTML demo?

Converting Markdown documentation into a live HTML demo involves transforming the Markdown source file into an HTML document, copying associated media assets, and then pushing the generated content to a GitHub Pages branch for hosting.

How do I update my GitHub Pages site when new UnityCtl commands are added?

To update your GitHub Pages site when new UnityCtl commands are added, you run a rebuild that regenerates the HTML demo from the updated Markdown source, ensuring the live demo reflects the latest features and command outputs.

Does this demo page generation process copy media assets alongside the HTML?

Yes, the demo page generation process copies media assets alongside the HTML output. When converting the Markdown source document into an HTML file, associated media assets are copied to ensure the published GitHub Pages site displays correctly.

Can I use this approach to rebuild and publish documentation without manual Git commands?

Yes, you can rebuild and publish documentation without manual Git commands by using an automated script. It handles the Markdown to HTML conversion and directly deploys the updated content to the gh-pages branch.

What are the limitations of using a script to deploy to the gh-pages branch?

A limitation of using a script to deploy to the gh-pages branch is that it specifically targets the GitHub Pages workflow. It requires a Markdown source document and focuses purely on HTML generation and asset copying for that specific hosting environment.