
Gpc Onboarding
- 19 installs
- 1 repo stars
- Updated August 1, 2026
- yasserstudio/gpc-skills
Helps with ai & agent building tasks.
About
gpc-onboarding is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- gpc-onboarding
- AI & Agent Building
- AI-coding skill
Gpc Onboarding by the numbers
- 19 all-time installs (skills.sh)
- Ranked #10,587 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yasserstudio/gpc-skills --skill gpc-onboardingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 19 |
|---|---|
| repo stars | ★ 1 |
| Last updated | August 1, 2026 |
| Repository | yasserstudio/gpc-skills ↗ |
What it does
Helps with ai & agent building tasks.
Files
GPC Onboarding
When to use
Use this skill when the task involves:
- A user running GPC for the very first time
- Guided first-run setup via
gpc quickstart - Interactive auth setup via
gpc auth loginwizard orgpc auth setup-gcp - Resolving failing doctor checks with
gpc doctor --fix - Configuring a default app or a second app profile
- General "how do I get started with GPC?" questions
Inputs required
- Whether the user has a service account JSON key already, or needs to create one
- The Android package name (e.g.,
com.example.app) - Whether this is a fresh machine or an existing partial setup
Commands
gpc quickstart
Guided setup flow. Idempotent — safe to re-run.
Step 1/4 Checking for existing config... ✓ Found profile "myapp"
Step 2/4 Verifying credentials... ✓ Service account valid
Step 3/4 Checking package name... ✓ com.example.app
Step 4/4 Running doctor... ✓ All checks passed
Ready. Here's what you can do next:
gpc status → app health snapshot
gpc releases list → current tracks
gpc reviews list → recent reviews
gpc vitals overview → crash and ANR ratesgpc quickstart is the recommended entry point for all new users. It detects existing config, validates credentials, confirms the package name, and runs a full doctor check — all in one flow.
gpc auth login (interactive wizard)
When run without flags in a TTY, gpc auth login prompts interactively:
1. Auth method: service account or ADC 2. Credentials file path (with validation loop — retries until a valid path is given) 3. Profile name (optional, defaults to "default") 4. Default package name
Use this when gpc quickstart fails at the credentials step, or when the user wants more control over how auth is configured.
gpc auth setup-gcp
Step-by-step service account creation guidance for users who do not yet have a GCP project or JSON key:
- Walks through creating a GCP project and enabling the Google Play Developer API
- Shows required IAM roles for the service account
- Explains how to grant the service account access in Play Console (Settings → API access)
- Guides downloading the JSON key file
- Verifies the result with
gpc auth status
Use this when the user is starting from zero -- no GCP project, no key file.
Shortcut if you already have the key:
gpc auth setup-gcp --key /path/to/service-account.jsonValidates the JSON, authenticates, and saves to config in one step.
gpc doctor --fix
Runs all doctor checks and applies inline remediation for each failing check.
gpc doctor # show current health
gpc doctor --fix # auto-fix what can be fixedEach failing check displays a suggestion. --fix applies those suggestions automatically where possible. Issues that require manual steps (e.g., Play Console API access grants) are shown with instructions but cannot be auto-fixed.
Procedure
0) Install GPC (if not already installed)
npm install -g @gpc-cli/cli1) Run gpc quickstart
This covers the majority of first-time setups:
gpc quickstartFollow the prompts. The wizard is idempotent — re-run it at any point.
2) If credentials are not yet set up
Option A — you already have a service account JSON key:
gpc auth loginOption B — you need to create a GCP project and service account from scratch:
gpc auth setup-gcp3) Fix remaining doctor issues
gpc doctor --fixReview any checks that still fail and follow the inline suggestions.
4) Verify
gpc statusA successful status output confirms GPC is fully configured and connected.
After successful setup
Once onboarded, common next commands:
gpc status-- app health snapshotgpc releases list-- view release tracksgpc vitals overview-- crash/ANR dashboardgpc reviews list-- recent user reviewsgpc verify-- check Android developer verification statusgpc docs list-- browse all 108 embedded documentation topics from CLI (v0.9.64+)gpc docs show <topic>-- read any guide offline in the terminalgpc docs search <query>-- full-text search across all docsgpc docs init-- write GPC.md quick-reference for AI agents
Enable tab completion (v0.9.58+): brew install yasserstudio/tap/gpc installs completion files automatically. For npm installs, run gpc completion bash >> ~/.bash_completion (or zsh/fish equivalent). Since v0.9.60 the scripts surface live profile/app/track values at TAB time.
Failure modes
| Symptom | Likely Cause | Fix |
|---|---|---|
gpc quickstart fails at Step 2 | Invalid or missing service account key | Re-run gpc auth login or gpc auth setup-gcp |
gpc doctor --fix can't fix an issue | Manual intervention needed | Follow the suggestion shown for that check |
| No package name found | App not configured | gpc config set app com.example.app |
| Auth wizard loops on file path | File path is wrong or file doesn't exist | Provide the absolute path to the JSON key |
gpc quickstart skips to Step 3/4 | Existing partial config found | Safe — it resumes from where setup left off |
Related skills
gpc-setup— detailed auth configuration, profiles, env vars, proxy setupgpc-troubleshooting— error codes, debug mode, common fixes
{
"skill_name": "gpc-onboarding",
"evals": [
{
"id": 1,
"prompt": "I just installed gpc and I have no idea where to start. I've never used it before. I have an Android app on Google Play (com.mycompany.myapp) but I don't have any service account set up yet. What do I do first?",
"expected_output": "Guides the user through the full first-run flow: gpc quickstart as the starting point, gpc auth setup-gcp to create a service account from scratch, and gpc doctor to verify everything is working",
"files": [],
"expectations": [
"Recommends gpc quickstart as the first command to run",
"Explains that gpc auth setup-gcp is available since the user has no service account yet",
"Mentions that gpc quickstart is idempotent and safe to re-run",
"Shows gpc doctor or gpc status as the verification step",
"Does not overwhelm with advanced options — keeps the flow beginner-friendly"
]
},
{
"id": 2,
"prompt": "I ran gpc quickstart and it failed at Step 2 — Verifying credentials. It says my credentials are invalid. I thought I downloaded the right JSON key from Google Cloud Console but something is wrong. How do I fix this?",
"expected_output": "Diagnoses the credential failure and walks the user through re-running auth setup, either via gpc auth login for an existing key or gpc auth setup-gcp for a fresh start, and explains how to grant Play Console access to the service account",
"files": [],
"expectations": [
"Identifies that the service account key itself may be valid JSON but the account may not have Play Console API access granted",
"Suggests running gpc auth login to re-enter credentials, or gpc auth setup-gcp to start fresh",
"Explains that Play Console access must be granted separately under Settings → API access",
"Recommends re-running gpc quickstart after fixing credentials",
"Mentions gpc auth status as a way to check the current auth state"
]
},
{
"id": 3,
"prompt": "I ran gpc doctor and I see 2 failing checks: one says 'Default app not set' and another says 'API connectivity failed'. I want to fix both automatically. Can I do that?",
"expected_output": "Explains gpc doctor --fix, shows what it can auto-fix (package name config), what may require manual steps (API connectivity / Play Console access), and how to verify after",
"files": [],
"expectations": [
"Tells the user to run gpc doctor --fix",
"Explains that the 'Default app not set' check can be auto-fixed or manually fixed with gpc config set app com.example.app",
"Explains that 'API connectivity failed' may require manual steps — granting the service account access in Play Console",
"Notes that --fix shows inline suggestions for anything it cannot auto-resolve",
"Recommends running gpc doctor again after applying fixes to confirm all checks pass"
]
},
{
"id": 4,
"prompt": "I'm already using gpc for my main app (com.company.mainapp) and everything is working. Now I want to add a second app profile for a different package name — com.company.secondapp — with its own service account key. How do I set that up without breaking my existing config?",
"expected_output": "Shows how to create a named auth profile for the second app using gpc auth login with a profile flag, configure the package name for that profile, and switch between profiles using gpc auth switch or --profile",
"files": [],
"expectations": [
"Explains that named profiles keep multiple apps isolated — existing config is not affected",
"Shows gpc auth login with a --profile flag to create the second profile",
"Shows how to set the default package name for the new profile via gpc config or .gpcrc.json",
"Shows gpc auth switch or the --profile per-command flag to use the second profile",
"Optionally mentions GPC_PROFILE env var for scripting"
]
}
]
}