Build Applicaster integrations with your AI agent

Each skill packages an entire Applicaster integration — the contract, the schemas, the edge cases and a test tool that proves your implementation against a running service. Install one into Claude Code, Cursor or any agent that supports Agent Skills, and it builds the integration with you.

npx skills add https://docs.applicaster.com

Or install a single skill:

• Cloud Events

  applicaster-cloud-events: use when implementing a new Applicaster Cloud Events receiver, auditing or hardening an existing one, adding a new documented or extension event type to a receiver, or resolving async/idempotency/ordering behavior for event handlers.
  npx skills add https://docs.applicaster.com --skill applicaster-cloud-events

  Read the skill · Guide · 25 files

• Get Context API

  Get Context API integration: use when building or hardening a customer-hosted backend for the Applicaster Context Setter Plugin — the GET endpoint(s) that populate storage_keys and, for authenticated/account-scoped data, persistent_keys. Works in any stack; establishes Remote-URL-only or Remote+Runtime scope, resolves per-namespace ownership, business-logic source, persistence and scope, and auth/delivery before edits, validates request AND response boundaries through the project's own validator, and ships a skill-local contract-driven context-setter-e2e tool that validates a running service against an approved contract.
  npx skills add https://docs.applicaster.com --skill applicaster-context-setter

  Read the skill · Guide · 18 files

• Continue Watching Feed

  Continue Watching and Favorites: use when adding cross-device Continue Watching or remote favorites to a Zapp Pipes library.
  npx skills add https://docs.applicaster.com --skill applicaster-continue-watching-favorites

  Read the skill · Guide · 15 files

• Implementing Login Flow with custom UI

  Use when building an Applicaster "custom UI" login flow — a customer-hosted website (shown in the app's webview on mobile) that runs your own login UI/UX and hands the tokens back to the app. Use it whenever the default Login Flow UI isn't enough — for full control over the login/registration screens, or to add third-party providers (Apple, Google, Facebook, SMS) the default flow doesn't support. Covers the exact postMessage handoff, the refresh-token URL, and the delete-account URL.
  npx skills add https://docs.applicaster.com --skill applicaster-custom-login-ui

  Read the skill · Guide · 2 files

• Implementing Pipes2 feeds Guide

  Implement or harden a customer-hosted Applicaster Pipes2 JSON content-feed service. Use for static collection feeds and, when explicitly selected, entry-driven dynamic feeds, search, and protected playback/Fetch Entry. Works in any stack, preserves existing DSP behavior, validates Pipes2 responses at the service boundary, and includes a black-box validator for a running service.
  npx skills add https://docs.applicaster.com --skill applicaster-dsp-content-feeds

  Read the skill · Guide · 16 files

• Implementing the "Login Flow API"

  Login Flow API integration: use when building or hardening a customer-hosted backend that implements the Applicaster Login Flow endpoints (login, register, refresh, reset, delete account) so the app's built-in Login UI can drive it (on-device surfaces such as Roku are one common driver). Works in any stack; asks whether the backend proxies an existing OIDC/OAuth2 provider (the usual ROPC case) or is custom auth, adds request AND response validation to every endpoint through the project's own validator, and ships a skill-local login-e2e tool that validates a running server against the contract.
  npx skills add https://docs.applicaster.com --skill applicaster-login-flow

  Read the skill · Guide · 12 files

• In-App Purchases and Storefront

  Payments & Storefront API integration: use when building or hardening a customer-hosted backend that implements the Applicaster Payments & Storefront provider endpoints (products feed, transactions/receipt validation, entitlements, user subscriptions) the in-app purchase plugin drives across the app's stores (Apple, Google Play, Amazon, Roku). Works in any stack; asks which stores/platforms and payment provider are in scope and whether receipt validation is synchronous (201) or asynchronous (202 + Location), adds request AND response validation to every endpoint through the project's own validator, and ships a skill-local payments-e2e tool that validates a running provider against the contract.
  npx skills add https://docs.applicaster.com --skill applicaster-payments-storefront

  Read the skill · Guide · 17 files

• Preference Selector Feeds

  Preference Selector integration: use when building, reviewing, or hardening a cross-platform Zapp selector for content preferences, UI language, push topics, or ordered multi-action settings. Establishes the selector contract before edits, chooses documented roles or actions, validates feeds against a versioned per-selector contract, and provides Zapp configuration and device verification steps.
  npx skills add https://docs.applicaster.com --skill applicaster-preference-selector

  Read the skill · Guide · 20 files

• Secured content with signed URLs

  Signed URL service integration: use when building or hardening the customer-hosted signing endpoint the Applicaster Video Preload plugin calls after Fetch Entry and immediately before playback, to swap the resolved stream URL for a short-lived signed one. Normally a thin adapter in front of a signing system that already exists (CDN token authentication, CDN signed URLs or cookies, a token-issuing service); when no such system exists and a Fetch Entry route is in scope, signing belongs inside that response instead and this service should not be built. Works in any stack. The response is JSON:API — application/vnd.api+json with data.attributes.stream_src — NOT a Pipes2 feed. Validates the request boundary (ctx, src_url, entitlements), enforces no-store caching on per-user signed URLs, and ships a signed-url-e2e tool that checks a running signer against the documented schema.
  npx skills add https://docs.applicaster.com --skill applicaster-signed-urls

  Read the skill · Guide · 15 files

• Video Preload API Integration Guide

  Video Preload / Fetch Entry API integration: use when building or hardening the customer-hosted endpoint the Applicaster Video Preload plugin calls immediately before playback to resolve one entry into playable form — entitlement-checked stream sources, DRM key systems, personalized ad macros, or extra metadata. Works in any stack. Enforces the single hardest rule of this integration: the entry returned by Fetch Entry must keep the SAME type.value as the origin feed entry that linked to it, or the player rejects it with 'no compatible source'. Validates the request boundary (ctx, entitlements) and the Pipes2 response boundary, and ships a video-preload-e2e tool that walks origin feed -> link.href -> preload response against a running service.
  npx skills add https://docs.applicaster.com --skill applicaster-video-preload

  Read the skill · Guide · 17 files