agentleFS
nikhonitnikhonit/social-media-api-skills/skills/app-store-api/SKILL.md

app-store-api

Skill3 starsChanged 3 months agoMIT-0View on GitHub

Apple App Store data toolkit via ScraperSocial — app metadata, user reviews, keyword search, category charts and storefront locations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    You need Google Play data: Use the google-play-api skill.

    line 48
  2. Very specific:

    Every script also accepts --limit, --cursor, --fields, --format and --fresh.

    line 75
  3. Distinctive:

    Every response uses the same envelope:

    line 83
  4. Very specific:

    Use app_search.js with a keyword, or get_app_list.js for ranked category lists.

    line 112

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Store API skill

Read public Apple App Store data as clean JSON. This App Store API skill returns app metadata, user reviews, keyword search results, ranked category lists and the storefronts an app is available in — the raw material for app store optimisation, competitor tracking and review analysis. Every endpoint here costs 1 credit, which makes it cheap to poll regularly.

This skill wraps 6 live App Store endpoints from the ScraperSocial API. Public data only, returned as clean JSON.

When to use this skill

  • You are doing ASO work: checking how an app ranks for a keyword, or what its listing says.
  • You need user reviews for an app to summarise sentiment or track a regression after a release.
  • You are building a competitor watchlist and want category charts over time.
  • A user pastes an App Store link and asks what the app is or how it is rated.

Do not use this skill when

  • You need App Store Connect data — sales, installs, crash reports or anything tied to a developer account. This reads the public storefront only.
  • You need Google Play data. Use the google-play-api skill; the two stores are separate endpoints with different app identifiers.
  • You want download or revenue estimates. The API returns what the storefront publishes; it does not model private metrics.

Setup

export SCRAPERSOCIAL_KEY=sk_live_...   # https://scrapersocial.com/app/keys

Signing up at scrapersocial.com/signup includes 100 free credits, no card required.

Permissions and scope

These scripts do exactly three things and nothing else: read one environment variable (SCRAPERSOCIAL_KEY), send HTTPS requests to https://api.scrapersocial.com (the host is a constant in the code, not configurable), and print JSON. They run as node scripts/<name>.js with no other shell use, no file writes and no persistence. call_endpoint.js accepts only the 6 documented /v1/app_store/ paths in the table below and refuses anything else before a request is made.

Scripts

ScriptWhat it doesInputCredits
get_app_info.jsGet Apple App Store app info.handle1 credit
get_app_list.jsList Apple App Store app list.query1 credit per app
get_app_reviews.jsList Apple App Store app reviews.handle1 credit per review
app_search.jsList Apple App Store app search.query1 credit per app
get_categories.jsList Apple App Store categories.none1 credit per category
get_locations.jsGet Apple App Store locations.none1 credit
call_endpoint.jsCall any /v1/app_store/ endpoint directlypath + paramsvaries

Every script also accepts --limit, --cursor, --fields, --format and --fresh. --limit is clamped to 50: above that the API returns an async job instead of data.

Example

node skills/app-store-api/scripts/app_search.js "meditation timer"

Every response uses the same envelope:

{ "data": {}, "meta": { "count": 20, "next_cursor": "..." }, "request_id": "a18e4ef88ad4b00b" }

meta appears on paginated endpoints only. Keep request_id — support traces calls with it.

Endpoints

EndpointInputReturnsCreditsPaginated
/v1/app_store/app-infohandleapp1 creditno
/v1/app_store/app-listqueryapp1 credit per appyes
/v1/app_store/app-reviewshandlereview1 credit per reviewyes
/v1/app_store/app-searchqueryapp1 credit per appyes
/v1/app_store/categoriesnonecategory1 credit per categoryyes
/v1/app_store/locationsnonereport1 creditno

Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.

FAQ

How do I get App Store reviews as JSON?

get_app_reviews.js takes the app handle and returns reviews at 1 credit per review. Use --limit to control volume and --cursor to page.

How do I find an app without knowing its ID?

Use app_search.js with a keyword, or get_app_list.js for ranked category lists. Both return handles you can pass to get_app_info.js.

Does this cover every country storefront?

get_locations.js returns the storefronts the API supports. App availability and rankings differ by storefront.

Is this an official Apple API?

No. ScraperSocial is independent and not affiliated with Apple. It returns publicly available App Store data only.

Links

Disclaimer

ScraperSocial is an independent product and is not affiliated with, endorsed by, or sponsored by any platform named in this repository. All product names, logos and brands are property of their respective owners. These skills return only publicly available data.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.