start-site

Trigger a GitHub MCP workflow to start a deployed site and monitor its status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a site that has been deployed but is not serving traffic by triggering the appropriate managed workflow and validating the outcome.

Core Features & Use Cases

  • Orchestrates a start action via the GitHub MCP onboarding workflow to reactivate a site and restore traffic.
  • Requires explicit operator confirmation before dispatch and provides status updates until completion.
  • Use case: recover a downed site by starting it through the onboarder workflow and verifying it comes back online.

Quick Start

Provide the site identifier and confirm the action to start the site.

Frequently Asked Questions about start-site

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

FAQPage Schema
How do I bring a deployed site back online after downtime?

To bring a deployed site back online, trigger a managed GitHub MCP workflow with the start action and monitor its progress to verify it resumes serving traffic. Explicit operator confirmation is required before dispatching the workflow.

How does the GitHub MCP workflow monitor site recovery progress?

The GitHub MCP workflow monitors site recovery progress by using actions_list and actions_get commands to track the workflow execution. It reports continuous status updates until the start action completes successfully or fails to reactivate the site.

Do I need explicit confirmation to trigger a site start action?

Yes, explicit operator confirmation is required to trigger a site start action. The workflow will not dispatch the GitHub MCP onboarding process to reactivate a downed site until the user provides confirmation to proceed with the recovery.

What is the best way to automate reactivating a downed site?

The best way to automate reactivating a downed site is to trigger the actions_run_trigger workflow with the start action. This orchestrates the recovery via the onboarder workflow and validates the outcome to ensure the site comes back online.

Can I use this workflow to start a site that has never been deployed?

No, this workflow cannot start a site that has never been deployed. It applies specifically to recovery scenarios where a previously deployed site must be reactivated and restored to serving traffic after experiencing downtime.