stop-site

Stop a site by name or domain via the Promaker managed-sites workflow.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/PromakerDev/promaker-plugin --skill stop-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stop-site
Source: https://github.com/PromakerDev/promaker-plugin/tree/main/plugins/promaker/skills/stop-site
Command: npx skills add https://github.com/PromakerDev/promaker-plugin --skill stop-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stop a site so it no longer responds to traffic until started again, enabling quick containment during incidents or maintenance.

Core Features & Use Cases

  • Stop a site by name or domain to take it offline across production or staging environments.
  • Track status via GitHub MCP workflow runs to confirm the shutdown and communicate outcomes.
  • Use case: pause a site during a deployment window or when investigating an outage without deleting data.

Quick Start

Confirm stopping the target site by providing its name or domain.

Frequently Asked Questions about stop-site

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

FAQPage Schema
How do I stop a site from responding to traffic during maintenance?

To stop a site from responding to traffic, you can pause it safely by providing its name or domain. This takes the site offline without deleting data until it is started again.

What is the best way to take a site offline for incident containment?

The best way to take a site offline for incident containment is to pause it by name or domain. This quickly stops the site from responding to traffic, enabling safe containment during outages.

How does the GitHub MCP workflow confirm a site shutdown status?

The GitHub MCP workflow confirms a site shutdown status by tracking workflow runs after the stop action is triggered. It reports on success or failure, communicating the outcome.

Can I pause a production site without losing its data?

You can pause a production site without losing its data by issuing a stop command using the site name or domain. The site stops responding to traffic until started again.

Does stopping a site across managed environments require specific identifiers?

Stopping a site across managed environments requires specifying the target site by its name or domain. This identifier applies the stop action across the managed-sites workflow.