onboard-site

Name: onboard-site
Availability: InStock
Author: Promaker

Collect client, repository, domain, and environment data to trigger Promaker onboarding workflows via GitHub MCP.

Updated Apr 19, 2026

Search Tags:#workflow #onboarding #github-mcp #site #promaker

Ready to run

npx skills add https://github.com/PromakerDev/promaker-plugin --skill onboard-site

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: onboard-site
Source: https://github.com/PromakerDev/promaker-plugin/tree/main/plugins/promaker/skills/onboard-site
Command: npx skills add https://github.com/PromakerDev/promaker-plugin --skill onboard-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish a new landing site to the Promaker managed platform by guiding a non-technical operator in Spanish through collecting the client, repository, domain, and environment, and by dispatching the onboarding workflow.

Core Features & Use Cases

Client handling: Checks for existing clients and creates a new client when needed, ensuring names are normalized to snake_case.
Domain & environment: Validates and normalizes the domain (with optional path) and maps the operator's environment choice to production, staging, or development.
Workflow dispatch: Triggers the onboarding workflow via GitHub MCP with the required inputs and tracks progress.
Progress & recovery: Provides status updates and guidance to restart or escalate if issues occur.

Quick Start

Inicia el flujo de onboarding de un nuevo sitio proporcionando el cliente, el repositorio, el dominio y el entorno.

Frequently Asked Questions about onboard-site

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

FAQPage Schema

How do I automate onboarding for a new landing site on a managed platform?▼

Automated site onboarding collects client, repository, domain, and environment data to dispatch a workflow. It validates inputs, normalizes client names to snake_case, and triggers the onboarding process via GitHub MCP to publish your landing site.

What inputs do I need to trigger an onboarding workflow for a new site?▼

Triggering an onboarding workflow requires tenant, repo, domain, and environment inputs, plus an optional tenant_display_name. The workflow uses these parameters to validate the client, map the domain, and publish the site to the chosen environment.

Can I use a custom domain path when publishing a site to staging or development environments?▼

Yes, custom domain paths are supported and validated during site onboarding. The environment choice maps to production, staging, or development, ensuring the domain and optional path are correctly configured for the target deployment.

How does client validation work when onboarding a new site?▼

Client validation checks for existing clients and creates a new one if needed. The system normalizes the client name to snake_case format, ensuring consistent repository and workflow triggering before dispatching the onboarding process.

What happens if the workflow dispatch fails during site onboarding?▼

If workflow dispatch fails, the onboarding process provides status updates and guidance for recovery. You can restart the workflow or escalate the issue based on the tracked progress and error feedback from the GitHub MCP integration.