edit-deployed-website

Modify and redeploy an existing deployed website using its workspace source path.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating an already published website normally risks losing the original node, URLs, or deployment configuration. This Skill guides the safe editing of an existing deployed site so changes are applied in place while preserving the original node and its primary and alias URLs. ## Core Features & Use Cases - Trusted Source Handling: Uses the Desktop Edit entry's node_id and workspace source_path directly, without downloading or checking out code. - Build and Test Workflow: Reuses the project's lockfile and package manager, runs affected tests, executes the real build command, and verifies a valid index.html output. - Safe Redeployment: Requires explicit user confirmation after warning about private cloud upload and the absence of a secrets scanner, then calls website_deploy with the existing node_id. - Use Case: A user wants to fix a typo and update the styling on their live site. The Skill edits the workspace source, rebuilds the project, and redeploys to the same node so the original URLs keep working. ## Quick Start Ask the agent to edit the deployed website opened from its page's Edit action, for example to change the homepage headline and redeploy it in place.

Frequently Asked Questions about edit-deployed-website

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

FAQPage Schema
How do I update an already deployed website without changing its URL?

Open the site from its page's Edit action so the workspace receives the trusted node_id and source_path, then make your changes and redeploy with website_deploy using the same node_id. This updates the site in place and preserves its primary and alias URLs.

What happens if the workspace source_path is missing when editing a deployed site?

The workflow stops and asks you to reopen the site from its page's Edit action. The node_id is never used to download source code, and no curl, OSS URL, or checkout tool is used as a fallback.

Does redeploying a website scan for secrets before upload?

No, there is currently no secrets scanner. Before publishing, the source_path is uploaded to private cloud storage, so you must confirm the source contains no secrets and give explicit publication confirmation.

Can I use this to publish a brand new website instead of editing one?

No, this workflow only updates an existing deployed site in place. It does not call republish, revoke, or delete the existing website, and it requires a valid node_id from the Desktop Edit entry.

Why does the build step matter before redeploying a website?

Running the project's real build command with its own lockfile and package manager verifies the changes compile correctly. The workflow also checks that a regular index.html exists at the build output root before any deployment is attempted.