{
  "skill_name": "app-store-optimization",
  "evals": [
    {
      "id": 1,
      "name": "language-app-full-plan",
      "prompt": "We are launching a language-learning flashcard app in English, German and Japanese. Build us an ASO plan: what goes in the name, subtitle and keyword field, how the product page should convert, which Custom Product Pages and events make sense, how we should test the page, and when the app should ask for a rating.",
      "expected_output": "Organizes the plan into visibility and conversion. Picks relevant, high-intent keywords over popular unrelated ones and lists name, subtitle, keyword field, primary category, ratings, Custom Product Page keywords and event cards as visibility levers without stuffing the description. For conversion covers the opening description lines, benefit-led first screenshots, current promotional text and research per locale. Maps Custom Product Pages to audiences or channels and mentions the 70-page capacity or assigned keywords. Proposes a test with one hypothesis, at most three treatments and chosen localizations. Places review prompts after positive moments and notes StoreKit may not show them.",
      "files": [],
      "expectations": [
        "Splits the plan into a visibility part and a conversion part",
        "Puts relevance and intent ahead of raw search volume",
        "Names name, subtitle, keyword field, category, ratings, Custom Product Page keywords and event cards as visibility levers, and keeps keywords out of the description",
        "Covers the description opening, benefit-first screenshots, up-to-date promotional text and keyword research per locale",
        "Ties Custom Product Pages to audiences or channels and mentions the 70-page limit or assigned search keywords",
        "Designs a test with one hypothesis, up to three treatments and selected localizations",
        "Asks for reviews after positive moments and says StoreKit decides whether the prompt appears"
      ]
    },
    {
      "id": 2,
      "name": "correct-aso-notes",
      "prompt": "Fix this internal ASO note: 'We can make 35 Custom Product Pages and they only work through links. Product page tests allow one treatment for all locales and give no confidence data. Words at the start of the keyword field rank higher. Add keywords to the description too. Event names are a hidden keyword field. Japan and Korea index the English keyword field, and a rating under 4.0 always kills conversion.'",
      "expected_output": "Raises the Custom Product Page limit to 70 and adds that assigned keywords let pages appear in search as well as via links. Says a test can have up to three treatments, localizations are selectable and App Analytics reports confidence. Rejects the idea that keyword position inside the field changes ranking, removes keywords from the description, and describes event names and short descriptions as visible card copy. Drops the unsupported claims about cross-locale indexing and a hard 4.0 threshold, while keeping research per market and treating ratings as a real signal.",
      "files": [],
      "expectations": [
        "Corrects the limit to 70 Custom Product Pages and adds assigned-keyword search visibility",
        "States up to three treatments, selectable localizations and confidence reporting in App Analytics",
        "Rejects the claim that position within the keyword field affects ranking",
        "Advises against adding keywords to the description",
        "Describes event metadata as visible card copy rather than a keyword field",
        "Removes the unsupported cross-locale indexing and fixed-threshold rating claims while keeping per-market research and ratings as signals"
      ]
    },
    {
      "id": 3,
      "name": "ownership-boundary",
      "prompt": "Our growth, compliance and payments teams keep arguing over who owns what on the App Store listing and the paywall. Split the work between ASO, App Store review and StoreKit, and say what ASO should still double-check.",
      "expected_output": "ASO keeps keywords, name and subtitle, description copy, screenshots and captions, promotional text, Custom Product Pages, events, page tests, listing localization and ratings. Rejection risk, screenshot compliance, PrivacyInfo.xcprivacy, metadata policy and ATT go to app-store-review. Paywall code, purchase handling, entitlements and product setup go to storekit. ASO still reviews listing copy and screenshots for accuracy and conversion, and never recommends competitor names, unrelated keywords or misleading screenshots.",
      "files": [],
      "expectations": [
        "Assigns keywords, name, subtitle, description, screenshots, captions, promotional text, Custom Product Pages, events, tests, listing localization and ratings to ASO",
        "Sends rejection risk, screenshot compliance, PrivacyInfo.xcprivacy, metadata policy and ATT to app-store-review",
        "Sends paywall code, purchase handling, entitlements and product setup to storekit",
        "Keeps an ASO cross-check of listing copy and screenshots for accuracy and conversion",
        "Never suggests competitor names, unrelated keywords or misleading screenshots"
      ]
    }
  ]
}