deploy-website

Deploy local website projects and standalone HTML files to a public URL.

1.3k|142|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/MiniMax-AI/minimax-code --skill deploy-website-minimax-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-website
Source: https://github.com/MiniMax-AI/minimax-code/tree/main/packages/local-runtime/assets/skills/deploy-website
Command: npx skills add https://github.com/MiniMax-AI/minimax-code --skill deploy-website-minimax-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a local website or a single HTML file to a public URL normally requires manual builds, staging, and upload tooling. This Skill automates the entire path from local source to a live public link, handling build detection, dependency staging, and safe publication. ## Core Features & Use Cases - Project Deployment: Detects the real build command and output directory from an existing frontend project, runs the build, and publishes the verified output. - Standalone HTML Publishing: Stages a single .html or .htm file with its required assets into an isolated workspace directory, rewriting relative URLs and imports so the page works when published. - Safety Controls: Verifies a regular index.html exists, blocks paths outside the workspace, avoids symlinks, and requires explicit user confirmation before making content public. - Use Case: You finished a portfolio page as portfolio.html with local CSS and images. Ask to deploy it, and the Skill snapshots the file and its assets into a staging folder, verifies the page, and returns a public URL. ## Quick Start Deploy my local website project in the current workspace to a public URL.

Frequently Asked Questions about deploy-website

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

FAQPage Schema
How do I deploy a local HTML file to a public URL?

Provide the path to your .html or .htm file and ask for deployment. The file is staged into an isolated workspace directory with its required assets, verified to have a working index.html, and published via the website_deploy tool which returns a public URL.

How do I deploy a frontend project like a static site?

Point the deployment at your project root. The existing lockfile and package manager are reused, the real build command from the project configuration is run, and the verified build output containing a root index.html is published.

Can I deploy an HTML file located outside my workspace?

Not directly. A separate source snapshot containing only the selected file and its required assets is first created inside the workspace, then staged and deployed. If the source cannot be accessed or copied safely, the deployment stops.

Is my source code uploaded when deploying a website?

Yes. The source_path is uploaded to private cloud storage alongside the public site files. Before publishing, you are asked to confirm the source contains no secrets and to explicitly approve making the website publicly accessible.

Why does website deployment fail for my HTML page?

Deployment stops if the target is missing, is a directory or symlink, lacks a regular root index.html, or has dependencies that cannot be resolved or copied safely. The unresolved dependency is reported instead of publishing a broken page.