asc-auth
Manage App Store Connect authentication using the `asc` CLI tool. Use this skill when: (1) Logging in with an API key: "asc auth login", "save my credentials", "set up authentication" (2) Managing multiple accounts: "asc auth list", "switch account", "use work account", "add another account" (3) Switching the active account: "asc auth use NAME", "switch to personal account" (4) Logging out: "asc auth logout", "remove credentials", "remove account" (5) Verifying current credentials: "asc auth check", "which account am I using?" (6) Updating account settings: "asc auth update --vendor-number", "save my vendor number" (7) Explaining the credentials file format (~/.asc/credentials.json) (8) Troubleshooting 401 auth errors or "missing credentials" errors
How do I install this agent skill?
npx skills add https://github.com/tddworks/asc-cli-skills --skill asc-authIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill manages Apple App Store Connect credentials locally using the asc CLI tool. It handles sensitive API keys and private keys, storing them in a dedicated configuration file at ~/.asc/credentials.json. While this is the intended purpose, it introduces a potential surface for indirect prompt injection via command arguments.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1/1 file flagged
What does this agent skill do?
asc auth — Multi-Account Authentication
Manages App Store Connect API key credentials in ~/.asc/credentials.json. Supports multiple named accounts with an active account that all asc commands use automatically.
Commands
login — save an account
asc auth login \
--key-id <KEY_ID> \
--issuer-id <ISSUER_ID> \
--private-key-path ~/.asc/AuthKey_KEYID.p8 \
[--name <alias>] # optional; defaults to "default"
[--vendor-number <number>] # optional; for sales/finance reports
--namemust not contain spaces (use hyphens or underscores, e.g.work-org)- If no
--nameis given, saves under"default" - The saved account is automatically set as active
- Saving to an existing name updates it (safe overwrite)
- Use
--private-keyinstead of--private-key-pathto pass raw PEM content --vendor-numberis optional; saved with credentials for auto-resolution by report commands
Output — AuthStatus JSON:
{
"data": [{
"affordances": {
"check": "asc auth check",
"list": "asc auth list",
"login": "asc auth login --key-id <id> --issuer-id <id> --private-key-path <path>",
"logout": "asc auth logout"
},
"issuerID": "abc-def-456",
"keyID": "KEYID123",
"name": "work",
"source": "file"
}]
}
list — show all saved accounts
asc auth list [--pretty] [--output table]
- Active account:
"isActive": true - Inactive accounts have a
"use"affordance to switch
Output — array of ConnectAccount:
{
"data": [
{
"affordances": { "logout": "asc auth logout --name personal", "use": "asc auth use personal" },
"isActive": false, "issuerID": "...", "keyID": "KEYID1", "name": "personal"
},
{
"affordances": { "logout": "asc auth logout --name work" },
"isActive": true, "issuerID": "...", "keyID": "KEYID2", "name": "work"
}
]
}
use — switch active account
asc auth use <name>
# → Switched to account "work"
Throws accountNotFound if <name> doesn't exist. Run asc auth list first to see valid names.
logout — remove an account
asc auth logout # removes the active account
asc auth logout --name work # removes a specific account
# → Logged out successfully
update — modify an existing account
asc auth update [--name <alias>] --vendor-number <number>
- Updates the named account (or active account if
--nameis omitted) - Currently supports
--vendor-number— the vendor number used bysales-reportsandfinance-reportscommands - Loads existing credentials, merges the update, and saves back
- Throws
accountNotFoundif the account doesn't exist
Output — AuthStatus JSON (includes vendorNumber):
{
"data": [{
"affordances": { "check": "asc auth check", "list": "asc auth list", ... },
"issuerID": "abc-def-456",
"keyID": "KEYID123",
"name": "work",
"source": "file",
"vendorNumber": "88012345"
}]
}
check — verify active credentials
asc auth check [--pretty] [--output table]
Shows active account name + source ("file" or "environment"). Shows vendorNumber if saved. No name field for environment credentials.
Credential Resolution Order
All asc commands resolve credentials in this order:
- Active account in
~/.asc/credentials.json(set byauth login/auth use) - Environment variables:
ASC_KEY_ID,ASC_ISSUER_ID,ASC_PRIVATE_KEY_PATH/ASC_PRIVATE_KEY_B64/ASC_PRIVATE_KEY
Credentials File Format
{
"accounts": {
"personal": { "issuerID": "...", "keyID": "KEYID1", "privateKeyPEM": "..." },
"work": { "issuerID": "...", "keyID": "KEYID2", "privateKeyPEM": "...", "vendorNumber": "88012345" }
},
"active": "work"
}
The vendorNumber field is optional — omitted from JSON when nil. It is used by sales-reports and finance-reports commands for auto-resolution when --vendor-number is not provided.
Legacy migration: Old single-credential files ({ "keyID": ..., "issuerID": ..., "privateKeyPEM": ... }) are automatically migrated to a "default" named account on first use.
Typical Workflows
First-time setup (single account)
asc auth login \
--key-id KEYID123 \
--issuer-id abc-def-456 \
--private-key-path ~/.asc/AuthKey_KEYID123.p8
asc auth check --pretty # verify source: "file"
asc apps list # works without env vars
Multiple accounts (personal + work)
# Add accounts
asc auth login --key-id K1 --issuer-id I1 --private-key-path ~/.asc/personal.p8 --name personal
asc auth login --key-id K2 --issuer-id I2 --private-key-path ~/.asc/work.p8 --name work
# List all
asc auth list --pretty
# Switch
asc auth use personal
asc apps list # now uses personal account
asc auth use work
asc apps list # now uses work account
Save vendor number for reports
# During login
asc auth login --key-id K1 --issuer-id I1 --private-key-path key.p8 --vendor-number 88012345
# Or add to existing account
asc auth update --vendor-number 88012345
# Now reports auto-resolve vendor number
asc sales-reports download --report-type SALES --sub-type SUMMARY --frequency DAILY
Remove an account
asc auth list # find the name
asc auth logout --name personal
asc auth list # confirm removal
Error Reference
| Situation | Resolution |
|---|---|
accountNotFound("ghost") | Run asc auth list to see valid names |
| Name contains spaces | Use hyphens/underscores: --name my-org |
| 401 Unauthorized on API calls | Run asc auth check to verify active credentials |
| No credentials anywhere | Run asc auth login or set ASC_KEY_ID env var |
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/tddworks/asc-cli-skills/asc-auth">View asc-auth on skillZs</a>