alizeeblack-code/google-play-store-lookup

Google Play Store Lookup

Look up a public Google Play Store listing from an app name.

This skill is currently a beta workflow. For status, strengths, and known limitations, read references/beta-notes.md when you need to explain reliability or caveats.

Inputs

Accept:

• app name
• optional region/country code (default us)
• optional language code (default en)
• optional developer name to disambiguate
• optional output mode:
  • links: keep screenshot URLs as pure links
  • download-images: download screenshots locally, then send them as images when the chat surface supports image display

Primary workflow

1. Resolve the country and language.
   • Default to us + en unless the user specifies another market.
2. Prefer the agent-browser powered lookup script:

python3 scripts/google_play_lookup_agent_browser.py --country <country> --lang <lang> --app-name "<app name>"

Optional developer hint:

python3 scripts/google_play_lookup_agent_browser.py --country <country> --lang <lang> --app-name "<app name>" --developer "<developer>"

3. If agent-browser is unavailable or fails, fall back to:

python3 scripts/google_play_lookup.py --country <country> --lang <lang> --app-name "<app name>"

4. If the script returns multiple candidates, ask the user to choose unless one is an obvious exact match.
5. If the script returns one strong result, summarize it for the user.
6. Return the result in this order by default:
   • App basic information
   • One-line positioning
   • Summary of what the app does
   • Main features
   • Core selling points
   • Screenshots
7. If the user asks for screenshots, do not use browser viewport screenshots of the page.
   • First extract original app screenshot resource URLs with:

python3 scripts/extract_screenshot_urls.py --query "<app name>" --country <country> --lang <lang>

• Then choose the output mode:
  • links: return the original screenshot URLs as plain links, one per line, with no bullets or numbering
  • download-images: save screenshots locally with scripts/download_screenshots.py, then return them as chat images when supported

Output format

When a match is found, return:

• App name
• Country / language used
• Google Play URL
• Developer
• Category / content rating when available
• Rating
• Rating count
• Price / install status text when available
• Install count when available
• One-line positioning
• Summary of what the app does
• Main features
• Core selling points
• Screenshots in one of two modes:
  • links: screenshot URLs only
  • download-images: downloaded image files, ready to send back into chat

If no match is found:

• say that no confident Google Play match was found
• suggest giving the developer name, exact title, or Play Store URL

Notes

• Prefer the agent-browser script over ad-hoc scraping so the workflow stays consistent.
• The agent-browser script reads rendered Google Play pages and is the default path because Google Play markup is unstable.
• Use the lightweight HTML script only as a fallback.
• If Google Play page structure changes, update scripts/google_play_lookup_agent_browser.py first.
• If the user wants raw details, return the script JSON output in a readable form.
• Do not stop at the store short description. Expand the final response into a human-readable summary similar to the Apple App Store workflow:
  • one-line positioning
  • what the app does
  • main features
  • core selling points
• When the page only exposes a short description, infer the higher-level summary carefully from the app name, developer, rating/download signals, and visible store context. Be clear and practical; do not overclaim hidden features.
• To extract original screenshot URLs, run:

python3 scripts/extract_screenshot_urls.py --query "<app name>" --country <country> --lang <lang>

• To download screenshots after extraction or lookup, run:

python3 scripts/download_screenshots.py --input-json <json-file> --output-dir <target-dir>