Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/external-purchases
US web checkout via the StoreKit External Purchase Link entitlement — currently 0% Apple commission (litigation ongoing), how to ship it safely, and how to architect for a commission flip so a future ruling is a config change, not a rewrite.
Passed 17 of 22 test cases with the skill, and 15 of 22 without it.
2 fixed15 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are modeling revenue for our US iOS app assuming Apple takes a 27% commission fee on external web checkouts initiated from inside the application. Should we incorporate this 27% baseline fee into our immediate launch financial calculations?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that the current US commission rate under court order is 0%. | Missed | Passed |
The instructions your model reads when the skill loads.
On the US storefront, apps may link out to a web checkout for digital goods using the StoreKit External Purchase Link entitlement — and as of mid-2026, court orders have Apple's commission on those purchases at 0%, with the fee case still moving through district court. This is the largest indie revenue unlock of the era, and it is reversible by a ruling — so the engineering rule is: ship it now, architect it so a commission can be flipped on later.
Verify current state before relying on this: the entitlement terms, the commission rate, and the litigation status have each changed more than once. Treat every number here as "true as of 2026-07, re-check."
com.apple.developer.storekit.external-purchase-link + matching
Info.plist declaration — a bare Link("Buy", …) without it is still a rejection (see
app-store/rejection-handler §3.1.1).ExternalPurchaseLink /
disclosure sheet where required). Don't dark-pattern the IAP option away if you keep both.Design so that a future "Apple takes N% of external purchases initiated in-app" ruling changes a config value, not your codebase:
source=app, timestamp, storefront) — web-organic checkouts stay unstamped. If a
commission returns, it applies to a knowable, logged subset.CommissionPolicy (remote-configurable): rate, applies_to,test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.