github-onboarding
The github-onboarding skill guides users through establishing a GitHub connection in Nixopus when no valid connector exists. Use this skill when `get_github_connectors` returns empty results, providing cloud users with direct GitHub App installation steps or self-hosted users with GitHub App manifest setup instructions before proceeding to repository selection or deployment workflows.
git clone --depth 1 https://github.com/nixopus/nixopus /tmp/github-onboarding && cp -r /tmp/github-onboarding/api/skills/github-onboarding ~/.claude/skills/github-onboardingSKILL.md
# GitHub Onboarding
Use this when `get_github_connectors` returns empty or has no valid connectors. Do NOT continue the deploy flow or call `get_github_repositories` until the user has completed the GitHub connection.
## Cloud Users
Guide the user step by step:
1. Install the Nixopus GitHub App: https://github.com/apps/nixopus/installations/new
- For an organization: https://github.com/organizations/{org-name}/settings/apps/nixopus/installations/new
2. Select which repositories or the entire organization to grant access to.
3. After clicking Install, GitHub redirects back to Nixopus and the connection is saved automatically.
4. Once connected, come back and say "deploy my app" — Nixopus will list the repos and walk through deployment.
## Self-Hosted Users
Self-hosted users need to create their own GitHub App first:
1. Open the Nixopus dashboard and go to the Apps page.
2. The setup wizard will walk through creating a GitHub App using GitHub's app manifest flow.
3. Choose whether to create the app under a personal account or an organization.
4. After creating the app, install it on the desired repositories.
5. Once setup completes, come back and say "deploy my app" — Nixopus will list the repos and walk through deployment.
## Important
- Do NOT attempt `get_github_repositories`, `analyze_repository`, or any deploy steps until the connection is set up.
- NEVER ask the user whether they are on cloud or self-hosted. The [user-context] block always contains `instance: mode=cloud` or `instance: mode=self-hosted`. Use that directly. If mode is "cloud", give cloud steps. If mode is "self-hosted", give self-hosted steps.
- After the user says they've connected, call `get_github_connectors` again to verify before proceeding.Reference for all Nixopus API operations callable via nixopus_api(method, path, body)
Generate Caddyfile configurations for static sites and reverse proxies — SPA fallback routing, cache headers, compression, redirects, and error pages. Use when deploying a static site that needs custom Caddy configuration, or when the user needs SPA routing, caching, or redirect rules.
Generate docker-compose.yml for multi-service setups including databases, caches, and service dependencies. Use when the app needs a database, cache, message broker, or has multiple independently deployable services.
Size container memory and CPU limits, diagnose OOM kills and CPU throttling, and recommend resource adjustments by ecosystem. Use when containers are being OOM-killed, running slowly, or when setting initial resource limits for a deployment.
Build and deploy C/C++ applications — CMake, Meson, Ninja, and Dockerfile patterns. Use when deploying a C or C++ project, or when CMakeLists.txt or meson.build is detected.
Run database migrations safely during deployment — framework-specific commands, pre-deploy vs post-deploy timing, health gates, and rollback strategies. Use when the app has a database migration system and needs migrations run during deployment.
Build and deploy Deno applications — version detection, dependency caching, and Dockerfile patterns. Use when deploying a Deno project, or when deno.json or deno.jsonc is detected.
Sub-agent routing table — which agent handles diagnostics, machine health, infrastructure, GitHub, billing, and notifications. Load when the current task is not a direct deployment.