From bitrise-agentic-onboarding
Run the full Bitrise prospect onboarding journey end-to-end in a single session: sign up for a Bitrise account, register an app and run a first CI build, then publish a public install page via Release Management. Use this whenever the user expresses intent for a complete Bitrise evaluation — e.g., "onboard me to Bitrise", "I want to try Bitrise from scratch", "set me up on Bitrise end to end", "walk me through Bitrise", "give me the full Bitrise demo", "I want to go from zero to a shareable install link". Prefer this skill over the individual stage skills when the user signals they want the whole journey, not just one piece.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bitrise-agentic-onboarding:bitrise-onboard-end-to-endThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Drive the full Bitrise prospect journey in one session by orchestrating
Drive the full Bitrise prospect journey in one session by orchestrating three sub-skills in order:
bitrise-signup — anonymous registration via the MCP, ending with
a Bitrise PAT installed in the user's MCP config.bitrise-ci-onboarding — register the user's app in Bitrise CI,
connect the repo, set up signing credentials, trigger and watch the
first build.bitrise-release-management — register the app in Release
Management, upload the build artifact, surface the public install page
URL.Each sub-skill works on its own. This skill is the connective tissue: it gathers shared context once, runs the stages in sequence, and hands state between them so the prospect doesn't have to repeat themselves.
The prospect wants one outcome: "I went from no account to a shareable install link." Composing three skills sequentially keeps each stage focused and testable, while this orchestrator hides the seam between them. Without it, the user would have to manually invoke each skill and repeat workspace slugs and app slugs across them.
agentic-onboarding
branch. The hosted endpoint at https://mcp.bitrise.io doesn't yet have
the signup or signing-upload tools. If the user is on the hosted
version, route them to local stdio install first:
claude mcp add bitrise -- go run github.com/bitrise-io/bitrise-mcp/v2@agentic-onboarding.
No BITRISE_TOKEN needed at startup; the signup flow installs one.Before kicking off stage one, ask the user a few questions in one batch so the rest of the flow runs without interruptions. Don't ask them again later unless the answers don't apply.
main)..p12 +
.mobileprovision for iOS, or .jks/.keystore + alias + passwords
for Android. If they don't have these and just want to see a green
build, skip signing in stage 2 — the default Android config uses the
debug keystore, and iOS can build & test without distribution signing.Maintain these in a context dictionary you carry across the stages:
{
email, platform, repo_url, is_public, provider, default_branch,
bundle_id, store_app_name, signing_files: {...},
// populated as we go:
workspace_slug, api_token, app_slug, build_slug,
connected_app_id, installable_artifact_id, public_install_url
}
Don't put api_token in any chat output. Hold it during the config
update in stage 1, then drop it.
Run the bitrise-signup skill. Pass the email. When done, capture:
workspace_slug (from verify_registration or list_workspaces)Confirm with me and list_workspaces before moving on. If signup fails
(invalid email, expired OTP, MCP not reconnected), don't proceed to stage
2 — fix or stop.
Run the bitrise-ci-onboarding skill. Pass:
workspace_slug from stage 1platform, repo_url, is_public, provider, default_branch,
signing_filesCapture:
app_slugbuild_slug of the first successful buildIf the build fails, stop and surface the failure log with diagnosis. Don't roll into Release Management on a failed build — there's no artifact to publish.
Run the bitrise-release-management skill. Pass:
workspace_slugapp_slugplatformbundle_id as store_app_idstore_app_namebuild_slug (so the skill can pull the artifact from CI) OR a local
artifact path if the user has one handyCapture:
connected_app_idinstallable_artifact_idWhen all three stages succeed, summarize for the user:
https://app.bitrise.io/app/<app_slug>)Suggest a couple of natural next steps: invite teammates to the workspace
(invite_member_to_workspace), set up Slack/email notifications, or send
the install URL to a tester. Keep the suggestion short — the prospect
just sat through three stages, give them air.
Each stage has its own failure modes. The orchestrator's job is to fail loudly and helpfully:
register_app errored, fix the input and retry. If
the first build failed, surface the failing step and don't move to
stage 3. The build can be retried after a fix without redoing stage 1.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub bitrise-io/agentic-onboarding --plugin bitrise-agentic-onboarding