paywalls

PurposeHelps design and optimize in-app paywalls, upgrade screens, and feature gates to convert free users to paid. Uses value-first principles, trigger-point strategies, and copy templates. Produces high-converting upgrade flows that lift freemium and trial conversion without dark patterns.

Domains

Marketing

Forms

Style GuideWorkflow

Required Tools

—None

Languages

—No strong dependency

Package Manager

—N/A

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger Timing

When users need to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates — e.g. freemium→paid, trial→paid, limit reached, or tier upgrade moments.

Working Mechanism

Reads product-marketing context if present, then assesses upgrade context, product model, user journey.
Applies core principles (value before ask, show don't tell, friction-free, respect the no).
Provides paywall trigger strategies, screen components, copy templates, timing/frequency rules, and A/B test ideas.

Output

Concrete paywall/upgrade flow recommendations, copy, and layouts that lift free-to-paid conversion while preserving user trust.

Use Cases

Two Typical Use Cases

Scenario 01

Optimize trial expiration paywall

A SaaS founder notices free users rarely upgrade after trial. They use this skill to design a trial-expiration paywall with early warnings, value summary, and clear CTA. The skill provides copy and layout, helping recover trials into paid plans and increasing revenue per user without harming trust.

Scenario 02

Build usage-limit upgrade prompt

A product manager sees users hitting free limits but not upgrading. They use this skill to build a usage-limit paywall showing progress, plan comparison, and quick upgrade path. The skill guides timing and escape hatch design, reducing frustration and lifting limit-reached conversion.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md33.3%
references33.3%
other33.3%

▸skills/paywalls/
▸root
- ·SKILL.md
- ▸evals
  - ·evals.json
- ▸references
  - ·experiments.md

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

When It Triggers · How It Works · What It Produces

Trigger Timing

Working Mechanism

Output

Two Typical Use Cases

Optimize trial expiration paywall

Build usage-limit upgrade prompt

SKILL.md

Skill Composition

/paywalls

Two Typical Use Cases

Optimize trial expiration paywall

Build usage-limit upgrade prompt

SKILL.md

Skill Composition

When It Triggers · How It Works · What It Produces

Trigger Timing

Working Mechanism

Output