CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

0.5.0: mobile apps and games positioning (README, site, og image, skills, CLI, MCP, adapters), MCP tools for subscriptions and catalog diff, tests, changelog

Browse source
This commit is contained in:
CRTkafa 2026-10-11 01:47:09 +08:00
parent 205f65828f
commit c48eead0e0
51 changed files with 960 additions and 318 deletions
Download patch file Download diff file Expand all files Collapse all files

8
skills/store-health/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: store-health
description: Watch a released mobile game's crash and ANR health on both stores - Google Play Android vitals (user-perceived crash rate 1.09 % and ANR rate 0.47 % bad behavior thresholds, 8 % per device model) through the Play Developer Reporting API, App Store power and performance metrics, diagnostic signatures and TestFlight crash reports, a weekly Markdown report, and validate blockers when a threshold is crossed. Use when the user asks about crashes, ANRs, vitals, stability, a weekly health check, or why Play shows a quality warning.
description: Watch a released mobile app's or game's crash and ANR health on both stores - Google Play Android vitals (user-perceived crash rate 1.09 % and ANR rate 0.47 % bad behavior thresholds, 8 % per device model) through the Play Developer Reporting API, App Store power and performance metrics, diagnostic signatures and TestFlight crash reports, a weekly Markdown report, and validate blockers when a threshold is crossed. Use when the user asks about crashes, ANRs, vitals, stability, a weekly health check, or why Play shows a quality warning.
---
# Store health (crashes, ANRs, diagnostics)
@ -15,13 +15,13 @@ instead). `storebound validate` runs the same checks for live apps. MCP: `health
needs **View app information (read-only)** for the app. Scope used: `playdeveloperreporting`. Reference:
https://developers.google.com/play/developer/reporting/reference/rest
- **App Store**: the API key that storebound already uses (Admin, App Manager or Developer role reads metrics).
Metrics come from users who share analytics with developers; small games may show none.
Metrics come from users who share analytics with developers; small apps may show none.
## Read the numbers
- **Play bad behavior thresholds** (28-day average, user-perceived, checked daily; sources:
https://developer.android.com/topic/performance/vitals and Play Console Help answer 9844486):
user-perceived crash rate **1.09 %**, user-perceived ANR rate **0.47 %**, and **8 %** on any single phone model.
Over a threshold, Play can lower the game's visibility and show a warning on its store listing. storebound marks
Over a threshold, Play can lower the app's visibility and show a warning on its store listing. storebound marks
over = blocker, from 80 % of a threshold = warn.
- Daily values swing on small user counts; the 28-day user-weighted rate is what Play judges. Device rows with fewer
than 500 users are ignored.
@ -43,6 +43,6 @@ instead). `storebound validate` runs the same checks for live apps. MCP: `health
- storebound reads the Reporting API rates as fractions (0.0109 = 1.09 %). The API reference calls them a
"percentage of distinct users" without stating the scale (not verified against a live response yet): the first
time, compare one number with Play Console > Android vitals and report a mismatch.
- Never share crash logs that contain player data outside the team; never paste tester emails from TestFlight crash
- Never share crash logs that contain user data outside the team; never paste tester emails from TestFlight crash
reports into chats or issues.
- Nothing here changes the store: it is safe to run any time.