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.
npx skills add rshankras/claude-code-apple-skills --skill store-signals --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Store Signals 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. ## Where it fits (read the seams) - **Not `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. - **Read-only on ASC.** Never responds to reviews, never mutates metadata/pricing. It surfaces, gates on explicit OK, and routes the change to the right command (`next-version`, `bugfix`, `metadata`). - **Feeds planning.** Output is a dated backlog appended to `ROADMAP.md` + rows in `SIGNALS.md`, consumed by `/apple:next-version` / `/apple:release`. ## Prerequisites - A live (or TestFlight) app; resolve its `appId` from `.planning/STATE.md`, else `list_apps` + confirm. - `.planning/` context
- Where it fits (read the seams)
- Prerequisites
- Flow
- Portfolio mode
- Done
- Caveats
What does the store-signals skill do?
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.
How do I install it?
Run `npx skills add rshankras/claude-code-apple-skills --skill store-signals --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.