solomd: Skill for Claude Code

Store submission over the Unzoo browser

Google Play and Microsoft Partner Center are the two channels with no usable API for this account, so releasing to them means driving a real browser. This skill is the accumulated way to do that without losing an afternoon.

Apple does not belong here. iOS and macOS submit over the App Store Connect API with no browser at all:

./scripts/submit-for-review.sh --platform ios   --version X.Y.Z \
    --notes-dir app-store/release-notes/X.Y.Z --dry-run

Reach for the browser on Apple only if that script has failed for a reason you have actually diagnosed.

Preflight

S=.claude/skills/store-submit
$S/unzoo.sh status          # {"browser_connected":true,...}
$S/unzoo.sh up              # starts the browser if it is down
$S/unzoo.sh tabs            # find the console tab that is already signed in

If the daemon is down, start it from a Bash call with run_in_background: true — nohup … & is not enough, it dies with the tool's shell:

"/Applications/Unzoo Browser.app/Contents/MacOS/unzoo-service" --daemon

browser_connected: false while the daemon is up means every navigate and evaluate will return HTTP 500; unzoo.sh up opens the browser and waits.

The six rules

These are not style preferences. Each one has already cost a session.

1. Pin the tab. Always. Without tab_id the API acts on whatever tab the user is looking at — their mail, their bank. Resolve one and export it:

export UNZOO_TAB=$($S/unzoo.sh find-tab play.google.com/console)

If a read comes back nonsensical, check unzoo.sh url before you debug the page. It has been the user's Cloudflare dashboard.

2. A coordinate click goes to the ACTIVE tab, not to tab_id. The endpoint accepts the id and ignores it. Clicking a background tab produces no click event, no error, and a page that looks like it ignored you. unzoo.sh click and click-el activate first for this reason — if you call /api/v1/click directly, activate yourself.