Agent skill · rudrankriyam
asc-analytics-reports
Collect, download, and verify App Store Connect Analytics reports with asc. Use when users need to discover analytics report requests, select report instances by processing date or granularity, download every segment, or verify downloaded files against Apple's size and MD5 metadata before analysis.
What it needs
About 4k tokens when loaded.
What this skill does
asc analytics reports Collect a complete set of analytics report segments and verify the compressed files before handing them to a separate analysis workflow. Do not interpret, aggregate, or present the report contents as part of this skill. Guardrails Treat report inventories, signed URLs, downloaded segments, and identifiers as confidential business data. Prefer an existing request. Creating a request changes App Store Connect state and requires an Admin-authorized profile; obtain explicit user approval before running asc analytics request. Never delete or replace a request as part of collection. Use asc analytics download; do not fetch or persist signed segment URLs separately. Store private files outside the source repository with owner-only permissions. Do not claim the collection is complete if any expected segment is missing or fails verification. 1. Verify the CLI contract Inspect the installed command before authentication or collection: Continue only when help lists --processing-date, --granularity, --paginate, and --include-segments. These filters require asc 3.5.0 or newer. If either filter is absent, ask the user to upgrade. Do not substitute the deprecated --date flag because it uses legacy local matching rather than Apple's server-side processing-date filter. 2. Prepare private storage Create a private temporary directory outside the repository before capturing JSON or downloading segments: Redirect command output and errors into this directory. Do not paste raw inventory JSON or error output into chat, commits, issues, or pull requests. 3. Find an existing request Resolve the app ID and selected asc profile, then list every request: Inspect the JSON structurally and select an existing usable request. Do not rely on --state when discovery works without it. If no usable request exists, stop and ask whether the user wants to create ONGOING or ONETIMESNAPSHOT access. State the target app and profile before requesting approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rudrankriyam/asc-analytics-reports