Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments.

MITAuto-check passedMarketing & SEO

Install Suede Paywalls

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-paywalls -a claude-code

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

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-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/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-paywalls .claude/skills/suede-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
suede-paywalls
GitHub stars
127
Token cost
~1.6k tokens
SKILL.md length
722 words
Files
5 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments.

  • Works in 3 steps: Upgrade Context - Freemium → Paid? Trial… → Product Model - What's free? What's… → User Journey - When does this appear?…
  • The user needs trigger timing
  • SKILL.md covers Initial Assessment, Paywall Trigger Points, Paywall Screen Components and Specific Paywall Types, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Paywalls is an agent skill from JasonColapietro/suede-creator-skills. Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments. Use when the user needs trigger timing, message structure, plan presentation, or experiment design after users have experienced value. NOT FOR: public pricing pages (use suede-site-alchemy), tier architecture (use suede-pricing), or cancellation and save flows (use suede-churn-prevention).

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).

It sits in Marketing & SEO, covering Landing pages, Referral and retention marketing and Experimental design. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.

When your agent uses it

  • The user needs trigger timing
  • Message structure
  • Plan presentation
  • Experiment design after users have experienced value

Example prompts

  • “/suede-paywalls”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  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?

What it can do on your machine

Read from SKILL.md and the folder at commit e5f94d7. 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

Suede Paywalls loads about 1.6k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 722 words of instructions outside code blocks.

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

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 JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 722 words, ~1,587 tokens.

Download SKILL.mdSave it as .claude/skills/suede-paywalls/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
suede-paywalls
description
Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments. Use when the user needs trigger timing, message structure, plan presentation, or experiment design after users have experienced value. NOT FOR: public pricing pages (use suede-site-alchemy), tier architecture (use suede-pricing), or cancellation and save flows (use suede-churn-prevention).
metadata.version
2.0.0

Suede Paywalls and Upgrade Moments

Suede designs in-product monetization around a truthful entitlement boundary and a value-aware moment, not interruption volume. Define when the user has enough context to evaluate an upgrade, what the paid change actually unlocks, and how to test the prompt without obscuring price, consent, or exit.

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?


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"


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]

Self-Critique Gate (run before delivering any screen copy)

Do not hand over a drafted paywall until you have re-read it against Anti-Patterns to Avoid and Boundaries below, and answered these out loud:

  1. Where is the close/dismiss control, and is it visible without scrolling or hovering?
  2. Is the price (including what renews, when, and at what amount) stated on the screen?
  3. Does any urgency claim ("ends today", a countdown) correspond to a real deadline?
  4. Can the user reach the free path in one tap from this screen?
  5. Does any copy assign blame, shame, or loss the user did not actually incur?

Name every hit before delivering. A hit on 1, 3, or 4 is a blocker: fix the draft, don't ship it with a caveat.


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

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

Defaults unless a running experiment says otherwise: ship these numbers, and say so when a test moves them:

  • Max 1 paywall impression per session.
  • Cooldown >= 7 days after a dismiss; >= 14 days after a second dismiss.
  • Suppress a given gate entirely after 3 lifetime dismissals.

Instead of "annoyance signals," instrument the ones a reviewer can read: dismiss rate per gate, post-paywall session-abandon rate, plus the impression, click-through, completion, revenue-per-user, and post-upgrade churn metrics the experiment reference tracks.


Upgrade Flow and Testing

Keep the path from paywall to payment in-context and pre-filled, and grant access the moment payment clears: the checkout and post-upgrade activation flow itself belongs to suede-onboarding.

For frequency, trigger-timing, copy, and price-presentation experiments: including which of the above defaults are worth testing first: See references/experiments.md. Use suede-ab-testing to design and read out the test.


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

Boundaries

  • Do not fabricate entitlement, plan, price, conversion, trial, or usage-limit data.
  • Do not change billing, entitlements, app configuration, experiments, or live paywalls without explicit authorization.
  • Do not recommend hidden close controls, confusing consent, forced continuity, obstructive cancellation, or false urgency.
  • Do not decide refund, tax, legal, platform-policy, accessibility, or billing-risk terms for the user.

Routing

  • Use suede-churn-prevention for cancel and save flows.
  • Use suede-site-alchemy for public pricing pages and suede-pricing for tier architecture.
  • Use suede-onboarding to reach first value and suede-ab-testing to validate paywall variations.

© JasonColapietro, 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 4 other files (references) in skills/suede-paywalls of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/experiments.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede 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.

Suede Paywalls compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Paywalls this skillJasonColapietro/suede-creator-skills127—~1.6kAutomated safety check: PassMIT
Ab Test ArchitectLeoYeAI/openclaw-master-skills2.2k—~5kAutomated safety check: PassMIT
Referral Programkostja94/marketing-skills1k—~1.5kAutomated safety check: PassMIT
Experiment Coachgrowthack88/growth-marketing-os116—~2.8kAutomated safety check: PassMIT
Ab Test Setup And Analysisirinabuht12-oss/marketing-skills4.1k—~739Automated safety check: PassNone
19 Ab Test Setupminhnv0807/ai-business-skills609—~3.6kAutomated safety check: PassMIT

Similar skills

  • Ab Test Architect

    LeoYeAI/openclaw-master-skills

    Plan, prioritize, and design rigorous A/B tests using the Test Velocity Method.

    2.2k GitHub stars~5k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Referral Program

    kostja94/marketing-skills

    When the user wants to plan, implement, or optimize referral program strategy.

    1k GitHub stars~1.5k tokensUpdated 5 days ago
    Marketing & SEOAuto-check passed
  • Experiment Coach

    growthack88/growth-marketing-os

    Experiment Coach — validates ideas before launch and runs growth experiments after it, from inside the chat.

    116 GitHub stars~2.8k tokensUpdated today
    Marketing & SEOAuto-check passed
  • Ab Test Setup And Analysis

    irinabuht12-oss/marketing-skills

    Designs statistically valid split tests for ads, audiences, landing pages, or bid strategies.

    4.1k GitHub stars~739 tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed
  • 19 Ab Test Setup

    minhnv0807/ai-business-skills

    Dung khi can test co ky luat de biet phuong an nao thang that — chon dung mot bien de test, viet gia thuyet, tinh sample size, setup tracking, doc y nghia thong ke va ghi test log cho ads, landing…

    609 GitHub stars~3.6k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed
  • Ad Creative Builder

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix…

    2.9k GitHub starsUsed in 2 repos~2.2k tokens
    Marketing & SEOAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo
  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes
  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes
  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed
  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

Questions about Suede Paywalls

What does Suede Paywalls do?

Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments. Suede Paywalls is an agent skill from JasonColapietro/suede-creator-skills. Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments.

When should I use Suede Paywalls?

Suede Paywalls fits situations like: the user needs trigger timing; message structure; plan presentation; experiment design after users have experienced value.

How do I install Suede Paywalls in Claude Code?

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

How do I install Suede Paywalls in Codex?

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

Can I use Suede 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 JasonColapietro/suede-creator-skills --skill suede-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/suede-paywalls, .gemini/skills/suede-paywalls, .github/skills/suede-paywalls and .opencode/skills/suede-paywalls in your project.

What does Suede Paywalls need to run?

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

Does Suede 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 Suede 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 Suede Paywalls use?

Suede 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 Suede Paywalls use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 Suede Paywalls?

Skills that share tags, products or a category with Suede Paywalls: Ab Test Architect (LeoYeAI/openclaw-master-skills, 2.2k stars), Referral Program (kostja94/marketing-skills, 1k stars), Experiment Coach (growthack88/growth-marketing-os, 116 stars) and Ab Test Setup And Analysis (irinabuht12-oss/marketing-skills, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Paywalls?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.