Move a site to the correct client via Promaker's GitHub MCP workflow.
npx skills add https://github.com/PromakerDev/promaker-plugin --skill move-site
Please help me install this Agent Skill. Skill: move-site Source: https://github.com/PromakerDev/promaker-plugin/tree/main/plugins/promaker/skills/move-site Command: npx skills add https://github.com/PromakerDev/promaker-plugin --skill move-site
Re-homes a site published under the wrong client; prompts a non-technical Spanish-speaking operator for the site, the current client and the correct client, dispatches the move workflow and, when the source client is left empty, decommissions it. Use when the operator says me equivoqué con el cliente, lo puse en el cliente X pero era Y, mover el sitio a otro cliente, cambiar de cliente or similar.
Move a site from the incorrect client to the correct one using Promaker's GitHub MCP workflow.
High-intent search queries and answers about installing and using this skill.
To move a site to the correct client, the system validates the site name, lists existing clients, normalizes inputs to snake_case, and dispatches a move workflow via the GitHub MCP service. It tracks progress until completion and handles failures explicitly.
When moving a site to another client leaves the source tenant empty, the workflow decommissions the empty tenant. This occurs after the operator explicitly confirms the move and decommissioning request during the input validation phase.
Yes, a non-technical operator can change the client of a site without coding. The workflow guides Spanish-speaking operators through input collection and explicit confirmation, dispatching the GitHub MCP automation without requiring technical intervention.
The GitHub MCP workflow handles site move failures through explicit failure and cancellation handling. It tracks the move progress continuously and provides specific failure management if the workflow encounters issues during the site redeployment process.
To move a site from the wrong client to the right one, you need the site name, the current incorrect client, and the correct target client. The system validates these inputs and normalizes them to snake_case before dispatching the workflow.
harnessManage chaos experiments via Harness MCP to validate system resilience.
PromakerDevCollect client, repository, domain, and environment data to trigger Promaker onboarding workflows via GitHub MCP.
juliuss1907Connects Model Context Protocol servers to Hermes Agent for external tools and services.
PromakerDevTrigger a GitHub MCP workflow to start a deployed site and monitor its status.
