paywall-upgrade-cro SKILL.md skillA
paywall-upgrade-cro from leoyeai/openclaw-marketing-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leoyeai/openclaw-marketing-skills/paywall-upgrade-cro@git:20260317.f2d4600Pins git:20260317.f2d4600 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leoyeai/openclaw-marketing-skills
- Path
skills/paywall-upgrade-cro/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260317.f2d4600, committed Mar 17, 2026
- Size
- 5,769 bytes
- Repository stars
- 1,051
- License
- a license file GitHub does not identify
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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-context.md` exists (or `.agents/product-marketing-context.md` 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 …
Read the whole file at its exact version.
How to install
mdr add leoyeai/openclaw-marketing-skills/paywall-upgrade-cro@sha256:de4ce0899b4dcb7cThe line at the top of this page pins the label git:20260317.f2d4600, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zdydww6lyjvtaava)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 17, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5769 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
leoyeai/openclaw-marketing-skills · 1,051 stars · license a license file GitHub does not identify · pushed 2026-06-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zdydww6lyjvtaava GET https://markdownregistry.com/api/v1/resolve?ref=leoyeai/openclaw-marketing-skills/paywall-upgrade-cro GET https://markdownregistry.com/api/v1/blob/de4ce0899b4dcb7c97c68f1e25d01f627bcccf46e7751f39c3965beb5575039b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from leoyeai/openclaw-marketing-skills
Every file in leoyeai/openclaw-marketing-skills