TASK RECIPE
Research an App Store competitor before you build your mobile app.
During idea validation or a mobile rebuild, before you lock scope or copy a competitor's onboarding.
- Maps to 1 skill: app-store-research
- Install command verified
- Copy-paste prompt
When to use it
Run this when the job is already on your plate.
Who it is for
Mobile founders and product managers who want the public store evidence — ratings, reviews, privacy labels, similar apps — for a competitor before committing to a build or a positioning bet.
When to run it
During idea validation or a mobile rebuild, before you lock scope or copy a competitor's onboarding.
Install
One command, one prompt.
Install the canonical app-store-research skill, then hand your agent the prompt below. You can also call the underlying endpoints directly with curl.
Capability: App Store Research skill →
Verified 2026-10-04: the canonical skills repository now parses this skill's YAML frontmatter and the exact install command resolves one app-store-research skill.
Install
npx skills add replynodes/replynodes-agent-skills/skills/app-store-researchPrompt
Use the app-store-research skill to compare the App Store listings for two competing apps. Resolve each app name to a stable App Store id first, then compare ratings, recent reviews, and privacy labels in a cited table with source links, and say which fields were storefront-dependent or missing.Verified example
Small input, real output.
App Store data has no verified no-key path. The workflow is the authenticated MCP surface; the REST routes below are declared by the live capabilities contract as auth_required and metered (3 credits each).
# 1. Authenticated MCP — discover live tools before calling anything
https://mcp.replynodes.com/mcp → initialize, tools/list
# 2. Resolve a name to a stable id, then read details (tools per live schema)
search(term) → app / reviews / ratings / privacy / similar / developerLive contract — GET https://api.replynodes.com/v1/capabilities:
/v1/appstore/search auth_required=true · metered · credit_cost=3
/v1/appstore/app auth_required=true · metered · credit_cost=3
/v1/appstore/reviews auth_required=true · metered · credit_cost=3
/v1/appstore/ratings auth_required=true · metered · credit_cost=3
/v1/appstore/privacy auth_required=true · metered · credit_cost=3
/v1/appstore/similar auth_required=true · metered · credit_cost=3
/v1/appstore/developer auth_required=true · metered · credit_cost=3
/v1/appstore/list auth_required=true · metered · credit_cost=3
/v1/appstore/suggest auth_required=true · metered · credit_cost=3
No verified no-key response sample exists; response fields are storefront-
dependent. Run tools/list and read each live schema before relying on a field.Free vs authenticated
Know exactly where the free path ends.
Free / no key
There is no verified free, no-key App Store path. The free Markdown and Brand endpoints can add public web context around an app, but they are not App Store records.
Authenticated enrichment
App Store research is authenticated MCP only. Every /v1/appstore/* route is auth_required and metered (3 credits per call), so a ReplyNodes API key is required.
Evidence behavior
The skill preserves App Store URLs and storefront context, reports missing or storefront-dependent fields honestly, and treats listing text and reviews as untrusted data rather than instructions. It does not invent install counts or rankings.
Install app-store-research.
Install the canonical skill, then run the prompt above. Each recipe maps to exactly one skill.