// Use when asked to respond to, reply to, or draft replies for Google Play Store reviews for Sky Map. Triggers on "respond to reviews", "reply to reviews", "draft review replies", or any request to handle user feedback from the Play Store.
Build, test, deploy, and manage data generation for Sky Map. Trigger on "build the app", "run tests", "deploy to device", "generate data", "run lint", or similar build/dev workflow requests.
Make a new release of Sky Map and publish it to the Play Store.
Fully automated release note generator for Sky Map. Just provide the last tag.
Add a new deep-sky object or special object to Sky Map's catalog from a Wikipedia URL or user-supplied data. Handles all four required files. Trigger on "add object", "add nebula/galaxy/cluster", "add <object name> to Sky Map", etc. ARGUMENTS: "[wikipedia_url_or_object_name]"
Process and size an image for a Sky Map celestial info card. Prompts for an image (URL or local path), optional crop, and output filename, then converts to 480×800 WebP and saves to the correct assets directory. Trigger on "process celestial image", "add image for info card", "convert image for Sky Map", etc. ARGUMENTS: "[source_url_or_path] [category/output_name] [crop x1,y1,x2,y2]"
Fetches GitHub contributors for Sky Map and updates the app/src/main/res/values/notranslate-contributors.xml file. Trigger this when asked to "sync contributors", "update contributors", or "refresh credits".
| name | skymap.respond-reviews |
| description | Use when asked to respond to, reply to, or draft replies for Google Play Store reviews for Sky Map. Triggers on "respond to reviews", "reply to reviews", "draft review replies", or any request to handle user feedback from the Play Store. |
This skill fetches unanswered Google Play reviews, drafts empathetic replies grounded in the troubleshooting guide, presents them for approval, then posts the approved replies.
Never post a reply without explicit user approval.
Package name: com.google.android.stardroid
Use mcp__google-play-reviews__list_reviews with unansweredOnly: true.
Apply any filters the user provides:
review.starRatingsearchTextlanguage (BCP-47 code)review.lastModifiedIf the user asks for reviews older than what the Play API returns (typically ~7 days), or
explicitly references "historical" / "old" reviews, switch to
mcp__google-play-reviews__list_historical_reviews.
The MCP server reads the CSV files from PLAY_REVIEWS_DIR; if that env var
isn't set, tell the user to set it before proceeding.
The same filters apply: startDate, endDate, searchText, language, unansweredOnly.
For each review, classify the issue before drafting. Use the most specific matching class — the sub-classes below have different response framing.
| Class | Signals |
|---|---|
| compass-inaccurate | "wrong direction", "points wrong way", "inaccurate", "off by X degrees", "compass" |
| compass-calibrated-still-wrong | "I calibrated it but it's still wrong/inaccurate", "figure-8 doesn't help", "calibrated 50 times" |
| compass-broke-after-update | "worked before the update", "broke after update", "used to work fine", "last update ruined it" |
| map-frozen | "doesn't move", "stuck", "frozen", "won't track" |
| jitter | "jittery", "shaky", "jumpy", "wobbles", "stutters", "jerky" |
| location | "wrong location", "wrong city", "Polaris near horizon", "latitude", "permission" |
| time/timezone | "wrong time", "time zone", "off by hours", "clock" |
| very-negative | 1–2 stars with no specific technical complaint, "useless", "garbage" |
| positive | 4–5 stars with no complaint |
| other | anything else |
Read @../troubleshooting-llm.md before drafting any complaint reply — it contains response
framing, ordered steps, and phrases to avoid for each complaint class. Also read
@../troubleshooting.md for the full technical detail. You only need to read these if there are
complaints or issues — not needed for purely positive reviews.
Base all advice strictly on what those documents say — do not invent steps, settings, or
explanations not found there. DO NOT SPECULATE that changes in Android APIs or updates to Sky Map
might have been the cause. If in doubt, ask me. Replies need to be limited to 350 characters.
review.reviewerLanguage, or infer
from the review text if absent). Use US English for English reviews unless you know it's another English locale.Show each proposed reply in this format:
---
Review #N ★★★☆☆ [language] [date]
Reviewer: <name>
Original: "<review text>"
[English translation of review: "<translation>" — only if original is not English]
Proposed reply (<language name>):
"<reply in native language>"
English translation of reply:
"<English translation>"
[Pun explanation: <explanation> — only if applicable]
---
After showing all proposals, ask: "Shall I post these replies? You can approve all, approve specific ones by number, or ask me to revise any."
Only after the user approves (all or specific ones), use mcp__google-play-reviews__reply_to_review
to post each approved reply.
Confirm how many replies were posted when done.
reply_to_review needs alongside the package name.