Skip to content
SkillModel-led1,295 tokens in use

paywalls

Designs in-app paywalls and upgrade moments: feature gates, limit screens, trial expiry, screen components, timing and frequency rules, and a reference for mobile subscription apps.

61,712 stars on the repository MIT Licensecoreyhaines31/marketingskills · skills/paywalls
npx skills add coreyhaines31/marketingskills --skill paywalls
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing paywalls costs

78tokens idle
1,295tokens in use
3,820tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output5/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

paywalls helps an agent decide when and how to ask free users to pay. It sets four principles, value before the ask, showing the value, a friction-free path and respect for a no, and then lays out trigger points and screen components.

Two references hold experiment ideas and guidance for consumer iOS and Android subscription apps.

What You Get

  • Guidance on four trigger points: feature gates, usage limits, trial expiration and time-based prompts
  • A seven-part paywall screen layout from headline to escape hatch
  • Text mockups for feature lock, usage limit and trial expiration paywalls
  • Timing and frequency rules, including when not to show a paywall
  • A test plan with metrics, plus a reference for mobile subscription paywalls

Common Use Cases

  • Designing the screen shown when a free user hits a limit
  • Planning trial expiry warnings at seven, three and one day
  • Deciding how often to show an upgrade prompt after a dismissal
  • Reviewing a paywall for dark patterns
  • Setting up a paywall inside the onboarding of a subscription app

What Makes It Unique

It ties every paywall to a value moment and requires a visible way back, with cool-downs measured in days. It lists dark patterns to avoid, including hidden close buttons and fake countdowns, and it separates in-app upgrade screens from public pricing pages, which belong to other skills.

Under The Hood

The SKILL.md and two references are loaded as context. It ships no scripts and runs no commands. The agent reads the product marketing context file in your project when it exists. It reaches no services and writes no files. Output is written recommendations and text mockups of paywall screens.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers