Skill

status

Get a quick overview of your RevenueCat project configuration including apps, products, entitlements, offerings, and webhooks.

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 Status

Get a quick overview of your RevenueCat project configuration.

Description

This command provides a summary of your RevenueCat project including:

  • Number of apps and their platforms
  • Total products configured
  • Entitlements defined
  • Offerings and their packages
  • Webhook integrations

Usage

/rc:status [project_name]

Arguments:

  • project_name (optional): Name of the project to show status for. If not provided, shows status for all accessible 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 project_name (optional)
    • Project name matching is case-insensitive and supports partial matches
  2. Get Projects

    • Call mcp_RC_get_project to retrieve all accessible projects
    • If project_name is specified in arguments, filter projects by name (case-insensitive partial match)
    • If no matching project found, inform the user and list available projects
    • If no project_name provided, show status for all projects
  3. Gather Statistics for Each Project For each project (filtered or all):

    • Call mcp_RC_list_apps with the project_id
    • Call mcp_RC_list_products with the project_id
    • Call mcp_RC_list_entitlements with the project_id
    • Call mcp_RC_list_offerings with the project_id
    • Call mcp_RC_list_webhook_integrations with the project_id
  4. Present Summary Format the results as a clear status report:

    ๐Ÿ“Š RevenueCat Project Status
    ============================
    Project: {project_name} ({project_id})
    
    ๐Ÿ“ฑ Apps: {count}
       - {app_name} ({platform})
       ...
    
    ๐Ÿ“ฆ Products: {count}
       - {product_identifier} ({type})
       ...
    
    ๐Ÿ”‘ Entitlements: {count}
       - {entitlement_name}
       ...
    
    ๐ŸŽ Offerings: {count}
       - {offering_name} (current: yes/no)
       ...
    
    ๐Ÿ”— Webhooks: {count}
       - {webhook_name} โ†’ {url}
       ...
    
  5. Highlight Issues (if any)

    • Products not attached to any entitlement
    • Offerings without packages
    • Apps without products

Example Output

Example 1: Status for a specific project

/rc:status "Fitness Tracker"

Output:

๐Ÿ“Š RevenueCat Project Status
============================
Project: Fitness Tracker (proj8f7f2106)

๐Ÿ“ฑ Apps: 3
   - Fitness Tracker (app_store) - iOS
   - Fitness Tracker (Web) (rc_billing) - Web
   - Fitness Tracker (Stripe) (stripe) - Stripe

๐Ÿ“ฆ Products: 20
   - com.fitness.premium_monthly (subscription)
   - com.fitness.premium_yearly (subscription)
   - ...

๐Ÿ”‘ Entitlements: 1
   - Premium: Unlock all features

๐ŸŽ Offerings: 11
   - default (current: yes)
   - annual-promo
   - ...

๐Ÿ”— Webhooks: 1
   - Production Backend โ†’ https://api.myapp.com/webhooks/rc

โœ… Configuration looks healthy!

Example 2: Status for all projects (no project name)

/rc:status

Shows status for all accessible projects, one after another.

Example 3: No matching project

/rc:status NonExistentApp

Output:

โš ๏ธ No project found matching "NonExistentApp"

Available projects:
- Fitness Tracker
- Recipe App
- Photo Editor
- Music Player
- Task Manager
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