agentmods.dev

asc-build-check

asc-build-check is a skill for Claude Code from markdavidgan/apple-dev-skills. It costs 66 tokens per session (2,514 once invoked), scanned A, original, MIT.

A checker for recent Apple app builds in App Store Connect, Apple's service for testing and distributing apps. It shows whether a build passed and helps investigate build, test, signing, and provisioning failures.

In plain words
What is it for?
Use it to check CI status, find failed build steps, inspect failing tests and logs, or investigate signing certificates, provisioning profiles, and app capabilities.
Why use it?
A failed CI build can involve many different steps, and its cause may be buried in logs or test results. This gathers the relevant failure details and identifies common Apple account and configuration problems.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the apple-dev-skills plugin — 62 skills, 25 commands, 7 agents shipped together

not rated 5repo 10d ago A scan 66 tokens original MIT

Good fit Use it to check CI status, find failed build steps, inspect failing tests and logs, or investigate signing certificates, provisioning profiles, and app capabilities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markdavidgan/apple-dev-skills/asc-build-check
View source ↗ markdavidgan/apple-dev-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add markdavidgan/apple-dev-skills --skill asc-build-check
Clone the repo
git clone --depth 1 https://github.com/markdavidgan/apple-dev-skills

Made for: Claude Code.

Or install apple-dev-skills, the plugin that ships this one along with the rest of its 62 skills, 25 commands, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for asc-build-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/asc-build-check/github.svg)](https://agentmods.dev/skills/markdavidgan/apple-dev-skills/asc-build-check)
Your own site
<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/asc-build-check"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/asc-build-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for asc-build-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/asc-build-check"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/asc-build-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.02514
Opus 5 $0.00033 $0.01257
Sonnet 5 $0.00013 $0.00503
Haiku 4.5 $0.00007 $0.00251

Measured 5d ago against content hash 75c4b6d121b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

asc-build-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

platforms/claude/skills/asc-build-check/SKILL.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ASC Build Check

Inspect CI builds, diagnose failures, and manage Developer Portal signing using the App Store Connect MCP server.

Workflow

Step 1: Get Overview

Call asc_status to see all products and their recent build status.

If the user specified an app name, filter the output to that product.

Step 2: Identify Failures

Look for builds where completionStatus is not SUCCEEDED. Common statuses:

  • SUCCEEDED -- all good
  • FAILED -- build or test failure
  • ERRORED -- infrastructure/config issue
  • CANCELED -- manually stopped

If all builds are green, report success and stop.

Step 3: Drill Into Failures

For each failed build:

  1. Get build details: Call asc_get_build with the build run ID to see all actions (build, test, archive, etc.) and which ones failed.

  2. Get issues: Call asc_get_issues with the build run ID -- this is the fastest way to see all errors, warnings, and test failures in one call.

  3. Get test results (if test action failed): Call asc_get_test_results to see which specific tests failed.

  4. Get logs (if needed): Use asc_get_build_logs with the failed action ID to fetch build log artifacts. Then asc_download_artifact for specific log files.

Step 3b: Diagnose Export/Signing Failures

If errors include ExportArchiveStep failures ("Exporting for X Distribution failed"):

  1. Parallel local analysis — while calling asc_check_signing, dispatch an apple-dev-skills:explore agent (Fast tier: claude-haiku-4-5 / gpt-4.1-mini / gemini-3.0-flash / kimi-for-coding) to read local files simultaneously:
You (MCP calls)                    explore agent (local files)
asc_check_signing (bundle IDs)  ←→  find all *.entitlements files
asc_list_profiles               ←→  read xcconfig for CODE_SIGN_IDENTITY
asc_list_certificates           ←→  grep for com.apple.developer.* keys
         │                                     │
         └──────────── compare ───────────────┘

Read the full file on GitHub · 208 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 208 lines · 66 tokens per session scan A 75c4b6d121b6

Subscribe to this mod's changes

asc-build-check is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 66 tokens to every session and 2,514 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude CodeDebuggingMobileagent-skillsai-skillsapp-store-connectappleasccursor
Related

Other skills, from other repositories

asc-crash-triage

Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.

rorkai/app-store-connect-cli-skills · 60 tokens

asc-revenuecat-catalog-sync

Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.

rorkai/app-store-connect-cli-skills · 51 tokens

asc-localize-metadata

Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.

rorkai/app-store-connect-cli-skills · 60 tokens

asc-shots-pipeline

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…

rorkai/app-store-connect-cli-skills · 79 tokens

asc-metadata-sync

Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.

rorkai/app-store-connect-cli-skills · 39 tokens

asc-release-flow

Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and…

rorkai/app-store-connect-cli-skills · 71 tokens