reviews
Objective: Summarize many reviews
1. **Process available reviews**
* Note the number of reviews and remember that value as "number_reviews"
* Overall rating
* Rating distribution if visible
* It's possible there aren't any reviews, for example if a product is new or out of stock. If that's the case, don't include any review analysis in your response.
2. **Identify repeated patterns**
* Common positive themes
* Common complaints
* Frequency of each theme
3. **Support themes with evidence**
* Representative quotes for major themes
* Specific examples that illustrate points
4. **Evaluate trustworthiness**
* Do reviews seem genuine?
* Suspicious patterns (all 5-star, generic language)
* Verified purchase indicators
5. **Summarize overall sentiment**
* Would most reviewers buy again?
* Who loves it vs. who hates it?
6. **Handling exceptions**
Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should
* respond as best you can and
* acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request.
Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user.
7. **Final response**
If you have relevant info to share, your final response should follow standard writing guidelines, including:
* Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized).
* Favor simple sentences that use common words
If number_reviews is 0, your response should mention that there aren't any reviews and you should jump to the follow-on question.
**Overview:** [X] reviews, [Y] average rating
**Pros**
| Theme | Frequency | Example |
| :---: | :---: | :---: |
**Cons**
| Theme | Frequency | Example |
| :---: | :---: | :---: |
**Quality of reviews:** [Do they seem genuine?]
**Bottom line:** [Would most reviewers buy again?]
8. **Follow-up questions**
If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.The prompt acts as an interactive review generator for places listed on platforms like Google Maps, TripAdvisor, Airbnb, and Booking.com. It guides users through a set of tailored questions to gather specific details about a place. After collecting all necessary information, it provides a well-reasoned score out of 5 and a detailed review comment that reflects the user's feedback. This ensures reviews are personalized and contextually accurate for each type of place.
DD
High-end Prompt Engineering & Prompt Refiner skill. Transforms raw or messy user requests into concise, token-efficient, high-performance master prompts for systems like GPT, Claude, and Gemini. Use when you want to optimize or redesign a prompt so it solves the problem reliably while minimizing tokens.
Build advanced prompts, task specs, verification criteria, and Claude Code setup using Andrej Karpathy's spec / verifier / environment method. Use this skill whenever you need to spec out a task or project, tighten or rewrite a prompt, define verification or success criteria for agent output, or set up/update a knowledge base, skill, or guardrails for an agent.