Static Site Publisher

The problem

Sharing a local HTML project or generated report usually requires a manual dance of Git commits, CI/CD pipelines, or cloud console uploads. Developers need a way to move code from a local directory to a public URL in seconds without infrastructure overhead.

What it does

• Publishes a local directory of HTML, CSS, and JS to a live public URL.
• Handles anonymous 24-hour deployments for quick demos and mockups.
• Supports persistent hosting for portfolios or production sites using an API key.
• Verifies deployment status and content-type headers via automated preflight and post-flight checks.
• Automates the folder preparation to ensure correct root mapping and asset resolution.

Frameworks & tools

Works with any static site generator or vanilla frontend stack. Requires curl, jq, and file on the host system.

Why this beats prompting it yourself

This skill handles the multi-step create-upload-finalize lifecycle of the here.now platform, ensuring deployments aren't just "started" but actually live. It includes built-in verification logic to check for 200 OK responses and proper asset paths before reporting success.

Use cases

• Deploying a live preview of a landing page for client approval.
• Hosting a generated data dashboard or HTML report for stakeholders.
• Sharing a functional UI mockup or portfolio piece instantly.
• Creating a public endpoint for agent-to-agent file handoffs.

Known limitations

Only supports static assets. Cannot host server-side code (Node.js, Python, etc.) or databases. Anonymous deployments expire after 24 hours.