Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/store-signals
Close the post-launch loop — turn a live app's App Store signals (reviews, analytics, sales, crashes, listing conversion) into a metric-tagged backlog for the next version, AND verify whether last cycle's changes moved the metric they promised to move. Read-only on App Store Connect; every change is surfaced and routed to another command, never auto-applied. Use before planning the next version, on a monthly cadence, or ~1-2 weeks after shipping to check if a change worked.
Passed 16 of 19 test cases with the skill, and 5 of 19 without it.
and 16 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our signal collection indicates that impression-to-download conversion dropped sharply due to outdated store listing screenshots and copy gaps. Which action command should be recommended?
| Checked | Without skill | With skill |
|---|---|---|
| Routes the recommended next step to /apple:metadata. | Missed | Passed |
The instructions your model reads when the skill loads.
Pull what the shipped app is actually telling you and convert it into the next backlog — then verify whether last cycle's bets paid off.
This is the missing arc that turns build → ship into a loop:
ship → MEASURE → DIAGNOSE → next PLAN → build → ship → measure again…The ledger (SIGNALS.md) is what makes it a loop and not a monthly report.
analytics-interpretation. That interprets a metric you hand it (is 14% D7 good?). This
is the end-to-end operate loop: gather every signal → cluster → diagnose → write a metric-tagged
backlog → close last cycle's hypotheses. It uses analytics-interpretation's benchmarks.next-version, bugfix, metadata).ROADMAP.md + rows in SIGNALS.md,
consumed by /apple:next-version / /apple:release.appId from .planning/STATE.md, else list_apps + confirm..planning/ context: STATE.md, APP.md, POSITIONING.md (job-to-be-done + guardrails)..planning/SIGNALS.md if present — the OPEN hypotheses from prior runs (each with a target metric,
recorded baseline, and "check-after" date). See signals-ledger.md for the ledger + backlog formats.SIGNALS.md → the OPEN rows to verify in step 5.list_reviews (recent, lowest-star first; flag unanswered), get_review for detail.get_analytics_report: retention, funnel/conversion, acquisition, impression→download.
No report configured yet → setup_analytics_reports and note "retention/funnel lands next cycle."get_sales_report: proceeds/units vs trailing 7/30-day.get_diagnostics (crash/hang signatures) + get_perf_metrics (launch, memory, energy).list_beta_feedback_crashes if in TestFlight.get_metadata to spot ASO conversion problems against current copy.test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.