Agent skill

Reply Reviews

Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.

Apache-2.0Auto-check passedMobile

Install Reply Reviews

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/reply-reviews .claude/skills/reply-reviews && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .claude/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/reply-reviews .agents/skills/reply-reviews && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .agents/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/reply-reviews .cursor/skills/reply-reviews && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .cursor/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/timusus/Shuttle2.git --path .claude/skills/reply-reviews

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/reply-reviews .gemini/skills/reply-reviews && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .gemini/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/reply-reviews .github/skills/reply-reviews && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .github/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add timusus/Shuttle2 --skill reply-reviews -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install timusus/Shuttle2 reply-reviews --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/timusus/Shuttle2.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/reply-reviews .opencode/skills/reply-reviews && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "reply-reviews" agent skill from https://github.com/timusus/Shuttle2/tree/main/.claude/skills/reply-reviews into .opencode/skills/reply-reviews/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-reviews", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: reply-reviews
GitHub stars: 229
Token cost: ~1k tokens
SKILL.md length: 543 words
Files: 1
Skills in repo: 13
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.

Works in 2 steps: Fetch unreplied reviews → Draft one reply per review. Write them…
Asked to check Play reviews
Calls gh
Draft review replies

What it does

Reply Reviews is an agent skill from timusus/Shuttle2. Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post. Use when asked to check Play reviews, draft review replies, or reply to app store reviews.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering App store release. It works with Android. The repository describes itself as: Shuttle Music: a music player for Android and iOS. Plays local files and streams from Jellyfin, Emby, Plex and Navidrome/Subsonic, with Chromecast, Android Auto, EQ and replay… The licence is Apache-2.0.

When your agent uses it

Asked to check Play reviews
Draft review replies
Reply to app store reviews

Example prompts

“/reply-reviews”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Fetch unreplied reviews
Draft one reply per review. Write them to support/reviews/drafts-YYYY-MM-DD.json (today's

What it can do on your machine

Read from SKILL.md and the folder at commit 9cef5dd. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- play.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reply Reviews loads about 1k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 543 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~52
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from timusus/Shuttle2 at commit 9cef5dd, republished under its Apache-2.0 licence (© timusus). 543 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/reply-reviews/SKILL.md (or your agent's skills folder).

name: reply-reviews
description: Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post. Use when asked to check Play reviews, draft review replies, or reply to app store reviews.
user_invocable: true

Reply to Play Reviews

Fetch recent Google Play reviews for S2, draft a reply for each unanswered one, and stop for the owner's approval. Never post a reply without explicit approval.

API window: the Play Developer API reviews.list endpoint only returns reviews with text from roughly the last 7 days. Reviews older than that are invisible to this tool: the owner must answer them manually in Play Console.

Steps

Fetch unreplied reviews:
bash
```
support/scripts/play-reviews list --unreplied --json
```
If this fails with a 401/403, the reviews-reader service account's grant may still be propagating (can take up to 24h): report that and stop, don't retry in a loop.
Draft one reply per review. Write them to support/reviews/drafts-YYYY-MM-DD.json (today's date; this directory is gitignored) as a JSON array, one object per review:
json
```
{
  "reviewId": "...",
  "stars": 4,
  "reviewText": "...",
  "replyText": "...",
  "approved": false
}
```
Reply guidelines:
- Vary the sign-off so replies don't read as a bot: some end "Tim" or "Cheers, Tim", many have no sign-off at all. Vary openings too.
- Don't repeat the complaint back to them, and don't placate ("that's a real gap", "that's fair feedback", "I know it hurt"). Answer plainly with what's true or what's happening.
- Never invent facts about the owner or the project ("S2 is where all my work goes", "actively updated"). The owner is a solo indie dev with three young kids; it's fine to say that plainly when it explains slow updates, but don't overuse it.
- Specific to the review, but short. Only reference what they said when it adds something.
- Under 350 characters.
- No em or en dashes, and none of the stock phrases play-reviews bans (see BANNED_PHRASES). Run support/scripts/play-reviews lint <drafts file> and fix every hit before showing drafts.
- No promises of dates ("next release", "next week", etc.): commit to nothing time-bound.
- Thank the reviewer for praise in positive reviews.
- For bug reports, ask them to email developer@simplecityapps.com with details (device, steps to reproduce) so it can be investigated: don't try to diagnose or fix in the reply.
- For widget complaints specifically, say widget improvements are being worked on. Only say this because it is currently true: check before reusing this line if that ever changes.
- Never argue with a reviewer, even an unfair one. Acknowledge and move on.

Show full SKILL.md (186 more words)Show less

3a. File what the reviews report. For every bug or feature request in a review, search first (gh issue list --search "<two key words>" --state all --limit 5). If an issue exists, comment with the review's date and star rating; otherwise gh issue create with an android: title, label bug or story, and the date and star rating as the source. Leave out reviewer names and devices; the repo is public. If a draft reply promises something ("it's on the list"), the issue must exist before the reply is posted. List the issue numbers alongside the drafts.

Show the drafts to the owner and stop. Do not run reply or post-approved yet. Wait for the owner to review the drafts file and flip approved to true on the ones they want sent (editing replyText first if they want changes).
Post only on explicit approval. Once the owner confirms, run:
bash
```
support/scripts/play-reviews post-approved support/reviews/drafts-YYYY-MM-DD.json
```
This posts every entry with "approved": true and no "posted" flag, then marks each as posted in the file. Use --dry-run first if there's any doubt about what would be sent.

Files

Just SKILL.md in .claude/skills/reply-reviews of timusus/Shuttle2.

Open the folder on GitHubat commit 9cef5dd

Compare with similar skills

Reply Reviews next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reply Reviews compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Reply Reviews this skilltimusus/Shuttle2	229	—	~1k	Automated safety check: Pass	Apache-2.0	yesterday
Screenshotsshortcuts/locationjoystick	103	—	~3.1k	Automated safety check: Pass	MIT	4 days ago
Play Policy Insightsarindamxd/camerax-android	132	2 repos	~2.1k	Automated safety check: Pass	Apache-2.0	6 days ago
Pp Google Playmvanhorn/printing-press-library	2.1k	—	~3.4k	Automated safety check: Notes	Apache-2.0	yesterday
Cometchat Android V6 Productioncometchat/cometchat-skills	130	—	~1.7k	Automated safety check: Pass	MIT	3 days ago
Gplay Metadata Synchanamizuki/solopreneur	152	—	~1.4k	Automated safety check: Pass	MIT	12 days ago

Similar skills

Screenshots
shortcuts/locationjoystick
Refresh all wiki/Play Store gallery screenshots from a connected Android device.
103 GitHub stars~3.1k tokensUpdated 4 days ago
MobileAuto-check passed
Play Policy Insights
arindamxd/camerax-android
Automated auditor designed to verify Android applications against Google Play Policy domains.
132 GitHub starsUsed in 2 repos~2.1k tokens
MobileAuto-check passed
Pp Google Play
mvanhorn/printing-press-library
Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store…
2.1k GitHub stars~3.4k tokensUpdated yesterday
MobileAuto-check: notes
Cometchat Android V6 Production
cometchat/cometchat-skills
Ship a CometChat Android v6 app safely — server-minted auth tokens instead of the dev Auth Key, keeping credentials out of the APK, release-build and R8/ProGuard checks, user provisioning…
130 GitHub stars~1.7k tokensUpdated 3 days ago
MobileAuto-check passed
Gplay Metadata Sync
hanamizuki/solopreneur
Metadata and localization sync (including Fastlane format) for Google Play Store listings.
152 GitHub stars~1.4k tokensUpdated 12 days ago
MobileAuto-check passed
Gplay Migrate Fastlane
hanamizuki/solopreneur
Migration from Fastlane supply to gplay CLI using the gplay migrate fastlane command.
152 GitHub stars~1.2k tokensUpdated 12 days ago
MobileAuto-check passed

Questions about Reply Reviews

What does Reply Reviews do?

Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post. Reply Reviews is an agent skill from timusus/Shuttle2. Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.

When should I use Reply Reviews?

Reply Reviews fits situations like: asked to check Play reviews; draft review replies; reply to app store reviews.

How do I install Reply Reviews in Claude Code?

Run `npx skills add timusus/Shuttle2 --skill reply-reviews -a claude-code`. Or copy the skill folder (.claude/skills/reply-reviews in timusus/Shuttle2) into .claude/skills/reply-reviews in your project. Claude Code loads it when a task matches its description.

How do I install Reply Reviews in Codex?

Run `npx skills add timusus/Shuttle2 --skill reply-reviews -a codex`. Or copy the skill folder (.claude/skills/reply-reviews in timusus/Shuttle2) into .agents/skills/reply-reviews in your project. Codex loads it when a task matches its description.

Can I use Reply Reviews in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add timusus/Shuttle2 --skill reply-reviews -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reply-reviews, .gemini/skills/reply-reviews, .github/skills/reply-reviews and .opencode/skills/reply-reviews in your project.

What does Reply Reviews need to run?

Going by SKILL.md and its folder, Reply Reviews needs the command-line tools its instructions call (gh).

Does Reply Reviews access the network?

SKILL.md names 1 domain. As links in the text: play.google.com. This is read from the text; nothing was executed.

Is Reply Reviews safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reply Reviews use?

Reply Reviews is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reply Reviews use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reply Reviews?

Skills that share tags, products or a category with Reply Reviews: Screenshots (shortcuts/locationjoystick, 103 stars), Play Policy Insights (arindamxd/camerax-android, 132 stars), Pp Google Play (mvanhorn/printing-press-library, 2.1k stars) and Cometchat Android V6 Production (cometchat/cometchat-skills, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reply Reviews?

timusus (a GitHub user) maintains it in timusus/Shuttle2, which has 229 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: timusus/Shuttle2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Reply Reviews

Install Reply Reviews

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Reply to Play Reviews

Steps

Files

Compare with similar skills

Similar skills

Screenshots

Play Policy Insights

Pp Google Play

Cometchat Android V6 Production

Gplay Metadata Sync

Gplay Migrate Fastlane

More from timusus/Shuttle2

Android Coroutine Testing

Debug Receivers

Deploy Android

Check

Commit

Delegate Verbose

Questions about Reply Reviews

Install Reply Reviews

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Reply to Play Reviews

Steps

Files

Compare with similar skills

Similar skills

More from timusus/Shuttle2

Related

Questions about Reply Reviews