Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .claude/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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.
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 rshankras/claude-code-apple-skills --skill review-response-writer -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .agents/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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 rshankras/claude-code-apple-skills --skill review-response-writer -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .cursor/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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.
--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 rshankras/claude-code-apple-skills --skill review-response-writer -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .gemini/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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.
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 rshankras/claude-code-apple-skills --skill review-response-writer -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .github/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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 rshankras/claude-code-apple-skills --skill review-response-writer -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "review-response-writer" agent skill from https://github.com/rshankras/claude-code-apple-skills/tree/main/skills/app-store/review-response-writer into .opencode/skills/review-response-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-writer", 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
review-response-writer
GitHub stars
787
Token cost
~2k tokens
SKILL.md length
563 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
MIT
At a glance
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans.
Works in 5 steps: Shows you care - Active developer =… → Helps others - Future users read responses → Converts critics - Can change rating… → …
Responding to negative reviews
SKILL.md covers When This Skill Activates, Response Philosophy, Response Framework and Response Templates, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Review Response Writer is an agent skill from rshankras/claude-code-apple-skills. Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans. Use when responding to negative reviews, drafting templates for common review types, or improving review management strategy.
Its SKILL.md is about 2k 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. The repository describes itself as: Claude Code skills for Apple platform development (iOS, macOS, iPadOS) — product validation, code generation, App Store optimization, and more. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
1Shows you care - Active developer = trustworthy app
2Helps others - Future users read responses
3Converts critics - Can change rating with good response
4Provides feedback - Reviews reveal real issues
5Builds community - Creates loyal users
What it can do on your machine
Read from SKILL.md and the folder at commit 9ffb831. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
Write
Edit
Glob
Grep
AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Review Response Writer loads about 2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 563 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~64
When it runs· the whole SKILL.md, loaded when a task matches
~2k
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.
Download SKILL.mdSave it as .claude/skills/review-response-writer/SKILL.md (or your agent's skills folder).
name
review-response-writer
description
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans. Use when responding to negative reviews, drafting templates for common review types, or improving review management strategy.
allowed-tools
Read, Write, Edit, Glob, Grep, AskUserQuestion
last_verified
2026-07-16
review_by
2027-06-22
Review Response Writer
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans.
When This Skill Activates
User needs to respond to negative reviews
User wants templates for common review types
User asks about review management strategy
User wants to improve customer relationships
Response Philosophy
Why Respond?
Shows you care - Active developer = trustworthy app
Helps others - Future users read responses
Converts critics - Can change rating with good response
Provides feedback - Reviews reveal real issues
Builds community - Creates loyal users
When to Respond
Review Type
Respond?
Priority
1-2 stars with feedback
Yes
High
3 stars with suggestions
Yes
Medium
Bug reports (any rating)
Yes
High
4-5 stars with content
Yes
Low
4-5 stars generic praise
Optional
Low
Abusive/inappropriate
Report, don't respond
-
Competitor spam
Report, don't respond
-
Response Timing
Negative reviews and bug reports: 24-48 hours. Positive reviews: weekly batch is fine.
Follow up after fixing an issue to notify the reviewer.
Response Framework
The A.C.T. Formula
A - Acknowledge their experience
C - Clarify or provide solution
T - Thank them and invite continued feedback
Template Structure
[Greeting - use their name if signed]
[Acknowledge their frustration/praise]
[Address specific points they raised]
[Provide solution, workaround, or update info]
[Thank + future-focused closing]
[Sign-off with name/team]
Response Templates
Negative Review: Bug Report
Review: "App crashes every time I try to export. Waste of money. 1 star."
Response:
Hi [Name],
I'm really sorry about the export crashes — that's frustrating,
especially when you're trying to get work done.
We identified this issue and it's fixed in version X.X, which is
now available. If you update and still experience problems, please
reach out to support@yourapp.com and we'll help you directly.
Thank you for taking the time to report this. It helps us improve.
— [Your Name], [App] Team
Negative Review: Missing Feature
Review: "No dark mode? In 2024? Uninstalled."
Response:
Hi there,
You're absolutely right — dark mode is important, and we hear you.
Good news: dark mode is in active development and planned for our
next major update. If you'd like to be notified when it's ready,
drop us a note at support@yourapp.com.
Thanks for the feedback. We hope to welcome you back soon!
— [Your Name], [App] Team
Negative Review: User Error (Diplomatic)
Review: "Can't figure out how to do X. Bad design."
Response:
Hi [Name],
Thanks for reaching out. I can see how [X] might not be obvious
at first — we could definitely make it clearer.
Quick tip: you can access [X] by [simple instructions]. We're also
adding an in-app tutorial in our next update to help with this.
If you're still stuck, email us at support@yourapp.com and we'll
walk you through it.
— [Your Name], [App] Team
Negative Review: Pricing Complaint
Review: "Too expensive for what it does."
Response:
Hi [Name],
Thanks for sharing your thoughts on pricing. I understand — value
is important.
A few things that might help:
• We offer a free trial so you can test before committing
• The subscription includes [key benefits]
• We regularly run promotions — follow us @handle for updates
We're always working to add more value. If there's a specific
feature you'd find worth the price, we'd love to hear about it.
— [Your Name], [App] Team
Negative Review: Generic/Vague
Review: "Doesn't work. Terrible app."
Response:
Hi there,
I'm sorry to hear you're having trouble. We'd really like to help,
but need a bit more info to figure out what's going wrong.
Could you email us at support@yourapp.com with:
• What you were trying to do
• What happened instead
• Your device and iOS version
We respond quickly and will do our best to get you sorted.
— [Your Name], [App] Team
Positive Review: With Feature Request
Review: "Love this app! Would be perfect if it had X."
Response:
Thank you so much for the kind words! 🙏
Great suggestion on [X] — you're not the first to ask, and it's
on our roadmap. Can't promise exact timing, but it's coming.
If you have other ideas, we're all ears at feedback@yourapp.com.
Thanks for being a [App] user!
— [Your Name]
Positive Review: Simple Thanks
Review: "Great app, use it every day. 5 stars!"
Response:
Thank you! Reviews like this make our day. We're glad [App] is
helping you. If you ever need anything, we're here!
— The [App] Team
After Fixing a Bug
Review: [Previously reported bug]
Follow-up Response:
Hi [Name],
Quick update: the [issue] you reported has been fixed in version
X.X, now available in the App Store.
Thank you again for letting us know — you helped us make [App]
better for everyone.
If you get a chance to try the update, we'd love to know if it
resolved things for you.
— [Your Name], [App] Team
Tone Guidelines
Always
Be genuinely helpful
Stay professional but warm
Take responsibility (never blame user)
Be specific (not generic)
Keep it concise
Never
Be defensive or argumentative
Make excuses
Ignore valid criticism
Use corporate jargon
Copy-paste identical responses
Promise specific timelines you can't keep
Tone by Situation
Situation
Tone
Bug report
Apologetic, solution-focused
Feature request
Appreciative, forward-looking
Confusion
Helpful, educational
Angry review
Calm, empathetic
Positive review
Grateful, personable
Show full SKILL.md (216 more words)Show less
Difficult Situations
Abusive Reviews
Don't respond. Report to Apple instead if it violates guidelines — profanity, hate speech,
personal attacks, or clear spam.
Competitor Attacks
Signs of competitor spam:
Multiple similar reviews at once
No specific details
Account has reviewed many competing apps
Unrealistic claims
Action: Report to Apple, don't engage.
Impossible to Satisfy
Some users can't be pleased. After one genuine attempt:
Don't keep responding
Document for your records
Move on
Legal Threats
If a review contains legal threats:
Don't respond publicly
Consult with legal
Document everything
Metrics to Track
Response Metrics
Response rate (aim for 100% of actionable)
Response time (aim for <48 hours)
Follow-up conversion (ratings changed after response)
Review Response Writer 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.
Review Response Writer compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Review Response Writer this skillrshankras/claude-code-apple-skills
Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands.
Maintain a Docusaurus product manual whose prose, navigation, localized page trees, screenshots, coverage metadata, and release build must stay aligned with the application.
SwiftUI animation patterns including springs, transitions, PhaseAnimator, KeyframeAnimator, SF Symbol effects, scroll-driven effects, mesh gradients, text renderers, and shader effects.
Generates an app icon for macOS or iOS — a fast CoreGraphics placeholder and/or flat layered source art to finish in Icon Composer (the Liquid Glass / iOS 26+ standard).
Revenue beyond the single-app price tag — own-app bundles, Family Sharing as a conversion lever, cross-developer bundles & suites, and institutional licensing via Group Purchases / Apple School &…
Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans. Review Response Writer is an agent skill from rshankras/claude-code-apple-skills. Write professional, empathetic responses to App Store reviews that build trust and turn critics into fans.
When should I use Review Response Writer?
Review Response Writer fits situations like: responding to negative reviews; drafting templates for common review types; improving review management strategy.
How do I install Review Response Writer in Claude Code?
Run `npx skills add rshankras/claude-code-apple-skills --skill review-response-writer -a claude-code`. Or copy the skill folder (skills/app-store/review-response-writer in rshankras/claude-code-apple-skills) into .claude/skills/review-response-writer in your project. Claude Code loads it when a task matches its description.
How do I install Review Response Writer in Codex?
Run `npx skills add rshankras/claude-code-apple-skills --skill review-response-writer -a codex`. Or copy the skill folder (skills/app-store/review-response-writer in rshankras/claude-code-apple-skills) into .agents/skills/review-response-writer in your project. Codex loads it when a task matches its description.
Can I use Review Response Writer 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 rshankras/claude-code-apple-skills --skill review-response-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-response-writer, .gemini/skills/review-response-writer, .github/skills/review-response-writer and .opencode/skills/review-response-writer in your project.
What does Review Response Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Response Writer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, AskUserQuestion.
Does Review Response Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Review Response Writer 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 Review Response Writer use?
Review Response Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Response Writer use?
About 2k tokens (SKILL.md is roughly 7.9k 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 Review Response Writer?
Skills that share tags, products or a category with Review Response Writer: Aso Appstore Screenshots (adamlyttleapps/claude-skill-aso-appstore-screenshots, 1.8k stars), Asc Ppp Pricing (rorkai/app-store-connect-cli-skills, 1.1k stars), Maintain Docusaurus Manual (matthiasn/lotti, 1.2k stars) and Workbuddy Skin Studio (cdredfox/workbuddy-skin-studio, 197 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Response Writer?
rshankras (a GitHub user) maintains it in rshankras/claude-code-apple-skills, which has 787 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on July 24, 2026.