paywall-ab

Automate RevenueCat paywall A/B testing with a 3-day human-in-the-loop check-in loop.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Daisuke134/paywall-ab-skill --skill paywall-ab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paywall-ab
Source: https://github.com/Daisuke134/paywall-ab-skill/tree/main
Command: npx skills add https://github.com/Daisuke134/paywall-ab-skill --skill paywall-ab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This AI-assisted skill automates the end-to-end process of conducting RevenueCat Paywall A/B tests, including setup, automated notifications, and human-in-the-loop decision making, reducing manual coordination and time to insight.

Core Features & Use Cases

  • Setup: Creating RC Offerings and Paywalls, generating AI-crafted paywalls, and guiding you to start an experiment.
  • Check-in loop: Every 3 days, Slack notifications prompt for winner reporting and CVR checks.
  • Analyze & iterate: Analyzes winner copy, generates new variants, and prepares the next experiment.
  • Multi-app support: Handles multiple apps via apps.json; centralizes experiment state.

Quick Start

Install and configure the OpenClaw agent, RC MCP, Slack app credentials, and your apps.json; then start a new paywall AB test.

Frequently Asked Questions about paywall-ab

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate RevenueCat paywall A/B testing with Slack notifications?

Automated RevenueCat paywall A/B testing uses a 3-day human-in-the-loop check-in loop that sends Slack notifications to prompt for winner reporting and CVR checks, managing experiments end-to-end.

What is the process for setting up a RevenueCat paywall A/B test with AI?

The setup process for AI paywall A/B testing involves creating RevenueCat Offerings and Paywalls, generating AI-crafted paywall variants, and guiding you to start an experiment across multi-app environments.

Do I need a specific environment to run automated paywall A/B tests for multiple apps?

Running automated paywall A/B tests for multiple apps requires configuring the OpenClaw agent, RevenueCat MCP, Slack app credentials, and an apps.json file to centralize experiment state.

How does the check-in loop work for RevenueCat paywall experiments?

The check-in loop for RevenueCat paywall experiments sends Slack notifications every 3 days to prompt for winner reporting and conversion rate checks, enabling human-in-the-loop decision making.

Can I generate new paywall variants after analyzing an A/B test winner?

Yes, after analyzing the winner copy, the system can generate new paywall variants and prepare the next RevenueCat experiment automatically, allowing continuous iteration on your offerings.

What are the limitations of using a 3-day check-in loop for paywall A/B testing?

A limitation of the 3-day check-in loop for paywall A/B testing is that it requires manual human-in-the-loop decision making at each interval, preventing fully automated winner selection without scheduled Slack interaction.