# Asc In App Events

Create and localize App Store in-app events, upload event media, and submit or recover...

- Repository: https://github.com/rorkai/app-store-connect-cli-skills (1119 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-in-app-events -g -a claude-code -y`
Codex: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-in-app-events -g -a codex -y`
Cursor: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-in-app-events -g -a cursor -y`
Gemini CLI: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-in-app-events -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rorkai/app-store-connect-cli-skills`

## Description

Create and localize App Store in-app events, upload event media, and submit or recover event review submissions with asc. Use when managing in-app events, event card or details page assets, or event-specific submission errors.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# asc in-app events

Use `asc app-events` for the requested stages only. A localization, media upload,
or diagnostic request does not authorize creating or submitting another event.
Preserve the resolved app, event, platform, locales, and existing authorization.

## Inspect the target

Check `asc app-events --help` and the relevant subcommand help before execution.
Resolve the app ID and auth profile; inspect an existing event before changing it:

```bash
asc app-events list --app "APP_ID" --paginate --output json
asc app-events view --event-id "EVENT_ID" --output json
asc app-events localizations list --event-id "EVENT_ID" --paginate --output json
```

Use explicit `--output json` when parsing results; output defaults are TTY-aware.
Keep event IDs and localization IDs distinct.

## Prepare and create

- Choose the event badge and intended territories. Check help for accepted
  `--event-type`, `--purpose`, and `--purchase-requirement` values; do not infer
  that every value described in App Store Connect is supported by the CLI.
- Set future RFC 3339 dates: start before end, duration from 15 minutes to 31 days,
  and publish start no more than 14 days before the event and no later than start.
  The CLI parses timestamps but does not enforce all of Apple's schedule rules.
- Provide a deep link that opens the event's destination. Test the universal link
  or custom URL scheme in the intended app build; a registered scheme alone does
  not prove the destination works. Creation without a deep link can succeed even
  though the event is not ready for review.

Replace the date variables with the agreed schedule before creating:

The rest: https://github.com/rorkai/app-store-connect-cli-skills/blob/HEAD/skills/asc-in-app-events/SKILL.md