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.
npx skills add markdavidgan/apple-dev-skills --skill review-managementgit clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsWrote 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.
[](https://agentmods.dev/skills/markdavidgan/apple-dev-skills/review-management)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/review-management"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/review-management/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.
<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/review-management"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/review-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00104 | $0.02581 |
| Opus 5 | $0.00052 | $0.01290 |
| Sonnet 5 | $0.00021 | $0.00516 |
| Haiku 4.5 | $0.00010 | $0.00258 |
Grade A, and why
review-management 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Management
Turn App Store reviews from noise into signal — and respond in a way that recovers ratings, surfaces real bugs, and builds reviewer trust.
MCP Tools at a Glance
| Tool | What it does |
|---|---|
asc_list_reviews |
Fetch reviews by app, territory, rating, or date range |
asc_get_review_detail |
Load full body + metadata for a single review |
asc_respond_review |
Post a new developer response |
asc_update_response |
Edit an existing response |
asc_delete_response |
Remove a response (rarely needed; prefer editing) |
All tools accept the app's appId (the numeric App Store ID, not the bundle ID).
Core Workflow: List → Cluster → Triage → Respond → Ship
Step 1 — Pull Recent Reviews
asc_list_reviews(appId, territory="US", rating=null, limit=200, sort="mostRecent")
Start broad. Pull the last 200 reviews from your primary territory, unsorted by rating so you see the real chronological stream. Repeat for secondary territories if your user base is multilingual.
Filters to use situationally:
rating=1orrating=2— when a new build caused a spike in low ratingsterritory="JP"— when localizing or debugging region-specific issuessort="mostCritical"— when you want to prioritize damage control
Step 2 — Cluster by Theme
Read each review body and assign one primary bucket. Quantify:
| Bucket | Signal it maps to |
|---|---|
| Crash / hang | Engineering — pair with asc-build-check, performance-instruments |
| Bug / broken feature | Engineering backlog |
| Missing feature | Product roadmap |
| Pricing / paywall | Monetization — pair with paywall-design |
| UX confusion | Onboarding, IA, copy |
| Praise | Nothing to fix; optionally use in ASO copy (asc-aso) |
A review can touch two buckets; assign it to the dominant one.
Step 3 — Triage by Priority
Not all one-star reviews are equal. Score each cluster:
- Volume — how many reviews mention this theme?
- Recency — is this cluster growing week-over-week?
- Rating weight — crashes skew 1-star; UX confusion often lands at 2–3.
- Respondability — can you fix it now, acknowledge it honestly, or only apologize?
What ships with it
1 file 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.
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.
- 6d ago First seen · 258 lines · 0 tokens per session scan A c932a36302ca
review-management is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 104 tokens to every session and 2,581 once invoked, about $0.0005 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.
Other skills, from other repositories
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.
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.
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…
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.
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…
asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and…