asc-submission-health

asc-submission-health is a skill for Claude Code from hanamizuki/solopreneur. It costs 82 tokens per session (1,664 once invoked), scanned A, a copy of asc-submission-health, MIT.

A diagnostic workflow for finding why an App Store submission is blocked or stuck in review. It checks release readiness, identifies evidence for each blocker, and routes repairs through the appropriate method.

In plain words
What is it for?
Use it to investigate validation failures, unclear review status, stuck submissions, cancellations, and retry decisions.
Why use it?
It separates problems that can be fixed through the public API from those needing a web session or manual work. It also prevents a healthy release from being changed unnecessarily.

Skill for Claude Code

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

Part of the ios-dev plugin — 26 skills, 1 agent shipped together

Good fit Use it to investigate validation failures, unclear review status, stuck submissions, cancellations, and retry decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hanamizuki/solopreneur/asc-submission-health
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 hanamizuki/solopreneur --skill asc-submission-health
Clone the repo
git clone --depth 1 https://github.com/hanamizuki/solopreneur

Made for: Claude Code.

Or install ios-dev, the plugin that ships this one along with the rest of its 26 skills, 1 agent.

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-submission-health

README.md
[![agentmods](https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-submission-health/github.svg)](https://agentmods.dev/skills/hanamizuki/solopreneur/asc-submission-health)
Your own site
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-submission-health"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-submission-health/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-submission-health

Your own site · 80×15
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-submission-health"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-submission-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,664 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 100% copy Near-identical to another mod 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.00082 $0.01664
Opus 5.5 $0.00033 $0.00666
Sonnet 5.5 $0.00016 $0.00333
Haiku 4.5 $0.00008 $0.00166

Measured 20d ago against content hash dfbc2d970edd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

asc-submission-health 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 20d 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.

Origin

This is a copy

100% identical to asc-submission-health — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/claude/ios-dev/skills/asc-submission-health/SKILL.md · 175 lines

How it starts

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

App Store submission health

Use this skill to explain why a release cannot proceed and to manage an existing review submission. Hand healthy release execution back to asc-release-flow.

Ownership boundary

This skill owns:

  • readiness validation and blocker diagnosis;
  • public-API, web-session, and manual repair routing;
  • review status and history;
  • cancellation and retry decisions.

Do not stage, upload, publish, or submit a healthy release from this skill.

Answer order

  1. State whether the version is ready, blocked, or already under review.
  2. Name each blocker and the evidence that proves it.
  3. Separate public-API repairs from web-session and manual work.
  4. Give one next command. Do not dump the entire repair catalog.

Establish the target

  • Resolve APP_ID, the version string or VERSION_ID, BUILD_ID, platform, and any known SUBMISSION_ID.
  • Configure auth with asc auth login or ASC_* environment variables.
  • Use ASC_BYPASS_KEYCHAIN=1 only for repository tests and isolated verification, not normal user sessions.
  • Prefer IDs once the target is resolved; stop when app, version, or product resolution is ambiguous.

Diagnose readiness

Run the canonical readiness report first:

asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table

Use --version-id "VERSION_ID" when known. Add --strict when warnings must fail automation.

Ask the review-specific doctor for an ordered explanation:

asc review doctor --app "APP_ID" --version "1.2.3" --platform IOS --output table

Collect direct evidence when the report points at the build or version:

asc builds info --build-id "BUILD_ID" --output table
asc versions view --version-id "VERSION_ID" --include-build --include-submission --output table

For digital goods, run only the relevant product validator:

asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table

Treat the ordered remediation plan from asc validate as the repair queue. Fix and verify one class of blocker before moving to the next.

Read the full file on GitHub · 175 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 20d ago First seen · 175 lines · 82 tokens per session scan A dfbc2d970edd

Subscribe to this mod's changes

asc-submission-health is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 1,664 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to asc-submission-health, differing in 12 lines, and is treated as a copy.