Skill

apikey

Retrieve public API keys for SDK initialization. Use when the user needs or asks for API keys for their iOS, Android, or web app.

From rc
Install
1
Run in your terminal
$
npx claudepluginhub anthropics/claude-plugins-official --plugin rc
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

RevenueCat API Key

Retrieve the public API key for SDK initialization.

Description

Quickly get the public API key needed to initialize the RevenueCat SDK in your app. This is the key you use in your client-side code.

Usage

/rc:apikey [platform] [project_name]

Arguments:

  • platform (optional): ios, android, web, or all. Defaults to all.
  • project_name (optional): Name of the project to retrieve keys for. If not provided, shows keys for all projects.

Can be referenced as $ARGUMENTS in the skill.

Instructions

When the user invokes this skill, perform the following steps:

  1. Parse Arguments (from $ARGUMENTS)

    • Extract platform (default: all) and project_name (optional)
    • Arguments can be in any order (e.g., "ios DuoCam" or "DuoCam ios")
    • Platform keywords: ios, android, web, all
    • Project name: any other text (case-insensitive match)
  2. Get Projects

    • Call mcp_RC_get_project to get all projects
    • If project_name is specified, filter projects by name (case-insensitive partial match)
    • If no matching project found, inform the user and list available projects
  3. Get Apps for Each Project

    • For each selected project, call mcp_RC_list_apps to get all apps
  4. Filter by Platform (if specified in arguments)

    • ios โ†’ filter for app_store type
    • android โ†’ filter for play_store type
    • web โ†’ filter for rc_billing type
    • all โ†’ show all apps
  5. Get API Keys

    • For each matching app, call mcp_RC_list_public_api_keys with the project_id and app_id
  6. Present Results Format as copy-paste ready code snippets:

    For iOS (Swift):

    Purchases.configure(withAPIKey: "{api_key}")
    

    For Android (Kotlin):

    Purchases.configure(PurchasesConfiguration.Builder(context, "{api_key}").build())
    

    For Web:

    Purchases.configure({ apiKey: "{api_key}" });
    

Example Output

Example 1: All keys for all projects

/rc:apikey

Shows API keys for all apps across all projects.

Example 2: iOS keys for a specific project

/rc:apikey ios "Fitness Tracker"

Output:

๐Ÿ”‘ RevenueCat Public API Keys - Fitness Tracker
========================================

๐Ÿ“ฑ iOS App (Fitness Tracker App Store)
   API Key: appl_aBcDeFgHiJkLmNoPqRsTuVwXyZ

   Swift:
   Purchases.configure(withAPIKey: "appl_aBcDeFgHiJkLmNoPqRsTuVwXyZ")

โš ๏ธ  Remember: These are PUBLIC keys, safe to include in client code.
    Never expose your SECRET API keys in client applications.

Example 3: All keys for a specific project

/rc:apikey "Recipe App"

Shows all API keys (iOS, Android, Web) for the Recipe App project only.

Notes

  • Public API keys are safe to include in your app's source code
  • Each platform (iOS, Android, etc.) has its own API key
  • Use the appropriate key for each platform in your app
  • Project name matching is case-insensitive and supports partial matches
  • If you have multiple projects, use the project name parameter to filter results
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Stars2
Forks0
Last CommitFeb 2, 2026