RevenueCat Status

VerifiedSafe

Provides a quick summary of a RevenueCat project configuration, including apps, products, entitlements, offerings, and webhooks. Helps you instantly assess the state of your project and spot potential issues like products not linked to entitlements or offerings missing packages.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#revenuecat#project-status#configuration#overview#mobile-apps

Recommended for

Automated summary

Provides a quick overview of a RevenueCat project's configuration including apps, products, entitlements, offerings, and webhooks.

Strengths

  • Fast summary of the entire RevenueCat setup
  • Identifies potential issues like products without entitlements
  • Supports filtering by project name or showing all projects

Limitations

  • Requires API access and proper permissions
  • Read-only; cannot modify configurations
  • Depends on MCP tools for data retrieval
When to use it

When you need a quick health check or overview of your RevenueCat project configuration.

When not to use it

If you need to make changes to the RevenueCat configuration, as this skill is read-only.

Security analysis

Safe
Quality score90/100

The skill only reads project configuration via designated MCP tools and presents a summary. No external network calls, file system access, or destructive actions are performed. No sensitive data is exfiltrated.

No concerns found

How this analysis is made

Examples

Status for a specific project
Show me the RevenueCat status for the project 'Fitness Tracker'.
Status for all projects
List the status of all my RevenueCat projects.
Status with no matching project
What is the RevenueCat status for NonExistentApp?

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

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/revenuecat-status-mm78nnvy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/revenuecat-status-mm78nnvy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/revenuecat-status-mm78nnvy/download' --output '.skill-downloads/revenuecat-status-mm78nnvy/SKILL.md.part' && mv '.skill-downloads/revenuecat-status-mm78nnvy/SKILL.md.part' '.skill-downloads/revenuecat-status-mm78nnvy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/revenuecat-status-mm78nnvy/SKILL.md' && test -s '.skill-downloads/revenuecat-status-mm78nnvy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/status' && cp -R '.skill-downloads/revenuecat-status-mm78nnvy' '.claude/skills/status'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js β‰₯ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/revenuecat-status-mm78nnvy'

openskills read 'revenuecat-status-mm78nnvy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/revenuecat-status-mm78nnvy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills