New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Paywalls

by coreyhaines31 in coreyhaines31/marketingskills

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

MITAuto-check passedMarketing & SEO

Install Paywalls

skills CLI
$ npx skills add coreyhaines31/marketingskills --skill paywalls -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreyhaines31/marketingskills paywalls --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paywalls .claude/skills/paywalls && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
paywalls
GitHub stars
54k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
596 words
Files
3 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

  • Works in 4 steps: Value Before Ask → Show, Don't Just Tell → Friction-Free Path → …
  • Wants to create
  • SKILL.md covers Initial Assessment, Core Principles, Paywall Trigger Points and Paywall Screen Components, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Paywalls is an agent skill from coreyhaines31/marketingskills. When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/experiments.md`).

It sits in Marketing & SEO, covering Conversion rate optimization and Landing pages. The repository describes itself as: Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. The licence is MIT.

When your agent uses it

  • Wants to create
  • Optimize in-app paywalls
  • Upgrade screens
  • The user mentions paywall

Example prompts

  • “paywall,”
  • “upgrade screen,”
  • “upgrade modal,”
  • “/paywalls”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Value Before Ask
  2. Show, Don't Just Tell
  3. Friction-Free Path
  4. Respect the No

What it can do on your machine

Read from SKILL.md and the folder at commit b9ba399. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Paywalls loads about 1.4k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 596 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~173
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreyhaines31/marketingskills at commit b9ba399, republished under its MIT licence (© coreyhaines31). 596 words, ~1,446 tokens.

Download SKILL.mdSave it as .claude/skills/paywalls/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
paywalls
description
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
metadata.version
2.0.0

Paywall and Upgrade Screen CRO

You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before providing recommendations, understand:

  1. Upgrade Context - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?

  2. Product Model - What's free? What's behind paywall? What triggers prompts? Current conversion rate?

  3. User Journey - When does this appear? What have they experienced? What are they trying to do?

Core Principles

1. Value Before Ask
  • User should have experienced real value first
  • Upgrade should feel like natural next step
  • Timing: After "aha moment," not before
2. Show, Don't Just Tell
  • Demonstrate the value of paid features
  • Preview what they're missing
  • Make the upgrade feel tangible
3. Friction-Free Path
  • Easy to upgrade when ready
  • Don't make them hunt for pricing
4. Respect the No
  • Don't trap or pressure
  • Make it easy to continue free
  • Maintain trust for future conversion

Paywall Trigger Points

Feature Gates

When user clicks a paid-only feature:

  • Clear explanation of why it's paid
  • Show what the feature does
  • Quick path to unlock
  • Option to continue without
Usage Limits

When user hits a limit:

  • Clear indication of limit reached
  • Show what upgrading provides
  • Don't block abruptly
Trial Expiration

When trial is ending:

  • Early warnings (7, 3, 1 day)
  • Clear "what happens" on expiration
  • Summarize value received
Time-Based Prompts

After X days of free use:

  • Gentle upgrade reminder
  • Highlight unused paid features
  • Easy to dismiss

Paywall Screen Components

  1. Headline - Focus on what they get: "Unlock [Feature] to [Benefit]"

  2. Value Demonstration - Preview, before/after, "With Pro you could..."

  3. Feature Comparison - Highlight key differences, current plan marked

  4. Pricing - Clear, simple, annual vs. monthly options

  5. Social Proof - Customer quotes, "X teams use this"

  6. CTA - Specific and value-oriented: "Start Getting [Benefit]"

  7. Escape Hatch - Clear "Not now" or "Continue with Free"

Show full SKILL.md (232 more words)Show less

Specific Paywall Types

Feature Lock Paywall
[Lock Icon]
This feature is available on Pro

[Feature preview/screenshot]

[Feature name] helps you [benefit]:
• [Capability]
• [Capability]

[Upgrade to Pro - $X/mo]
[Maybe Later]
Usage Limit Paywall
You've reached your free limit

[Progress bar at 100%]

Free: 3 projects | Pro: Unlimited

[Upgrade to Pro]  [Delete a project]
Trial Expiration Paywall
Your trial ends in 3 days

What you'll lose:
• [Feature used]
• [Data created]

What you've accomplished:
• Created X projects

[Continue with Pro]
[Remind me later]  [Downgrade]

Timing and Frequency

When to Show
  • After value moment, before frustration
  • After activation/aha moment
  • When hitting genuine limits
When NOT to Show
  • During onboarding (too early)
  • When they're in a flow
  • Repeatedly after dismissal
Frequency Rules
  • Limit per session
  • Cool-down after dismiss (days, not hours)
  • Track annoyance signals

Upgrade Flow Optimization

From Paywall to Payment
  • Minimize steps
  • Keep in-context if possible
  • Pre-fill known information
Post-Upgrade
  • Immediate access to features
  • Confirmation and receipt
  • Guide to new features

A/B Testing

What to Test
  • Trigger timing
  • Headline/copy variations
  • Price presentation
  • Trial length
  • Feature emphasis
  • Design/layout
Metrics to Track
  • Paywall impression rate
  • Click-through to upgrade
  • Completion rate
  • Revenue per user
  • Churn rate post-upgrade

For comprehensive experiment ideas: See references/experiments.md

Anti-Patterns to Avoid

Dark Patterns
  • Hiding the close button
  • Confusing plan selection
  • Guilt-trip copy
Conversion Killers
  • Asking before value delivered
  • Too frequent prompts
  • Blocking critical flows
  • Complicated upgrade process

Task-Specific Questions

  1. What's your current free → paid conversion rate?
  2. What triggers upgrade prompts today?
  3. What features are behind the paywall?
  4. What's your "aha moment" for users?
  5. What pricing model? (per seat, usage, flat)
  6. Mobile app, web app, or both?
  • churn-prevention: For cancel flows, save offers, and reducing churn post-upgrade
  • cro: For public pricing page optimization
  • onboarding: For driving to aha moment before upgrade
  • ab-testing: For testing paywall variations

© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/paywalls of coreyhaines31/marketingskills.

  • SKILL.md
  • evals/evals.json
  • references/experiments.md

Open the folder on GitHubat commit b9ba399

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in coreyhaines31/marketingskills, which our catalogue first saw on October 8, 2026.

Compare with similar skills

Paywalls next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Paywalls compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Paywalls this skillcoreyhaines31/marketingskills54k1 repos~1.4kAutomated safety check: PassMIT
Paywall Upgrade Crofreekmurze/dotfiles1k15 repos~1.4kAutomated safety check: PassNone
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence
Paywall Upgrade CroLeoYeAI/openclaw-marketing-skills1k1 repos~1.4kAutomated safety check: PassCustom licence
Cro Optimizationognjengt/founder-skills427—~2.4kAutomated safety check: PassMIT
Page Crofreekmurze/dotfiles1k12 repos~1.4kAutomated safety check: PassNone

Similar skills

  • Paywall Upgrade Cro

    freekmurze/dotfiles

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

    1k GitHub starsUsed in 15 repos~1.4k tokens
    Marketing & SEOAuto-check passed

  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Paywall Upgrade Cro

    LeoYeAI/openclaw-marketing-skills

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

    1k GitHub starsUsed in 1 repo~1.4k tokens
    Marketing & SEOAuto-check passed

  • Cro Optimization

    ognjengt/founder-skills

    Analyzes landing pages and provides detailed CRO (Conversion Rate Optimization) recommendations.

    427 GitHub stars~2.4k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

  • Page Cro

    freekmurze/dotfiles

    When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts.

    1k GitHub starsUsed in 12 repos~1.4k tokens
    Marketing & SEOAuto-check passed

  • Cro

    Nexus-JPF/note-companion

    When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.

    870 GitHub starsUsed in 5 repos~1.5k tokens
    Marketing & SEOAuto-check passed

More from coreyhaines31/marketingskills

All 21 skills in this repo

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Auto-check passed

  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~2.8k tokens
    Auto-check passed

  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

  • Aso

    coreyhaines31/marketingskills

    When the user wants to audit or optimize an App Store or Google Play listing.

    54k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed

  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed

  • Lead Magnets

    coreyhaines31/marketingskills

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation.

    54k GitHub starsUsed in 5 repos~2.7k tokens
    Auto-check passed

Categories

Questions about Paywalls

What does Paywalls do?

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Paywalls is an agent skill from coreyhaines31/marketingskills. When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

When should I use Paywalls?

Paywalls fits situations like: wants to create; optimize in-app paywalls; upgrade screens; the user mentions paywall.

How do I install Paywalls in Claude Code?

Run `npx skills add coreyhaines31/marketingskills --skill paywalls -a claude-code`. Or copy the skill folder (skills/paywalls in coreyhaines31/marketingskills) into .claude/skills/paywalls in your project. Claude Code loads it when a task matches its description.

How do I install Paywalls in Codex?

Run `npx skills add coreyhaines31/marketingskills --skill paywalls -a codex`. Or copy the skill folder (skills/paywalls in coreyhaines31/marketingskills) into .agents/skills/paywalls in your project. Codex loads it when a task matches its description.

Can I use Paywalls in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/marketingskills --skill paywalls -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paywalls, .gemini/skills/paywalls, .github/skills/paywalls and .opencode/skills/paywalls in your project.

What does Paywalls need to run?

SKILL.md names no scripts, command-line tools or credentials: Paywalls is instructions for the agent only.

Does Paywalls access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Paywalls safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Paywalls use?

Paywalls is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Paywalls use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Paywalls?

Skills that share tags, products or a category with Paywalls: Paywall Upgrade Cro (freekmurze/dotfiles, 1k stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Paywall Upgrade Cro (LeoYeAI/openclaw-marketing-skills, 1k stars) and Cro Optimization (ognjengt/founder-skills, 427 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Paywalls?

coreyhaines31 (a GitHub user) maintains it in coreyhaines31/marketingskills, which has 53,618 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: coreyhaines31/marketingskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.