New: 97,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

Upgrade Flow Design

by rampstackco in rampstackco/claude-skills

Designing free-to-paid conversion flows for SaaS products. An agent skill from rampstackco/claude-skills.

MITAuto-check passedMarketing & SEO

Install Upgrade Flow Design

skills CLI
$ npx skills add rampstackco/claude-skills --skill upgrade-flow-design -a claude-code

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

GitHub CLI
$ gh skill install rampstackco/claude-skills upgrade-flow-design --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/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/upgrade-flow-design .claude/skills/upgrade-flow-design && 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
upgrade-flow-design
GitHub stars
935
Token cost
~4.6k tokens
SKILL.md length
2,206 words
Files
11 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Designing free-to-paid conversion flows for SaaS products. An agent skill from rampstackco/claude-skills.

  • Works in 12 steps: The free-tier decision. Freemium,… → Value-triggered-upgrade, not… → Trigger-moment design sound. Paywalls… → …
  • Value demonstration
  • SKILL.md covers What this skill covers, The free-tier decision:…, Paywall-everywhere vs… and Trigger-moment design: where…, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Upgrade Flow Design is an agent skill from rampstackco/claude-skills. Designing free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `references/churn-prevention-upstream.md` and `references/common-upgrade-failures.md`).

It sits in Marketing & SEO, covering Referral and retention marketing. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • Value demonstration
  • Upsell vs downsell
  • Churn prevention
  • Freemium conversion

Example prompts

  • “/upgrade-flow-design”

Workflow steps

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

  1. The free-tier decision. Freemium, free-trial, reverse trial, or no-free.
  2. Value-triggered-upgrade, not paywall-everywhere or free-forever-trap. Paywalls at moments of demonstrated value.
  3. Trigger-moment design sound. Paywalls connect to specific user-demonstrated value.
  4. Paywall presentation matches trigger intensity. Strong triggers warrant modal; soft triggers inline.
  5. Copy connects to the trigger. Specific value-prop tied to what the user just did.
  6. Upsell, cross-sell, downsell logic. When primary upgrade is declined, secondary paths exist.
  7. Win-back flows designed. Lapsed users have a clear re-engagement path.
  8. Churn prevention upstream. Upstream signals trigger prevention; downstream upgrade flow is one of multiple defenses.
  9. Plan structure clear. Tier count appropriate; each tier has clear audience-fit.
  10. Pricing-page coordinates with upgrade flow. Plan structure decisions reflected on the pricing page.
  11. Conversion as success metric. Not just paywall display; downstream conversion to paid.
  12. Maintenance discipline. Plans, paywalls, win-back flows updated alongside product and pricing changes.

What it can do on your machine

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

Upgrade Flow Design loads about 4.6k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 175 tokens; SKILL.md has 2,206 words of instructions outside code blocks.

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

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 rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 2,206 words, ~4,593 tokens.

Download SKILL.mdSave it as .claude/skills/upgrade-flow-design/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
upgrade-flow-design
description
Designing free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention. Also triggers when free-to-paid conversion is low, when paywalls are blocking the wrong moments, or when upgrade flows are being scoped for the first time.
category
growth-tooling
catalog_summary
Designing free-to-paid conversion flows. Distinguishes paywall-everywhere (gates everything aggressively) from free-forever-trap (no upgrade path surfaces)…
display_order
9

Upgrade Flow Design

A senior product marketing director's playbook for designing free-to-paid conversion flows in SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. The discipline of asking for the upgrade at the moment the user has a reason to say yes.

Most upgrade flows fail in one of two ways. They block meaningful product use behind paywalls so aggressively that users churn before reaching the moment that would justify paying. Or they offer a generous free tier with no upgrade path that ever surfaces; users get everything they need; conversion stays at single-digit percentages indefinitely.

The upgrade flows that work do something different. They surface paywalls at moments where the user has demonstrably gotten value. The user has hit a usage threshold, completed a flow, or otherwise demonstrated they are getting the product's promise. The upgrade ask is honest about what they get next; the user is positioned to say yes because the value is fresh.

The voice is the senior product marketing director who has watched conversion rates double when paywalls were re-timed and watched them collapse when more aggressive paywalls were added. Practical, opinionated about the moments that earn the upgrade ask, willing to call out when the product's free tier is too generous to convert.

When to use this skill: scoping a free-to-paid conversion flow for the first time, auditing paywalls that block conversion or never surface, designing the trigger moments that earn upgrade asks, or deciding plan structure that supports upgrades over time.

What this skill covers

This skill spans free-to-paid conversion flows in SaaS products. The growth-tooling distinctions:

  • lead-magnet-design is top-of-funnel email capture. This skill is free-to-paid conversion in-product.
  • funnel-flow-architecture is the cross-tool funnel architecture. This skill is the upgrade flow specifically.
  • upgrade-flow-design (this skill) is trigger-moment design, paywall presentation, plan structure, win-back, churn prevention.
  • landing-page-copy is pricing-page copy; lives downstream of this skill's plan-structure decisions.
  • pm-spec-writing is the spec for engineers building the upgrade flow.

The audience: product marketers, growth marketers, in-house product teams, agencies running SaaS conversion work for clients.

Out of scope: cross-funnel architecture (covered by funnel-flow-architecture); pricing-page copy (covered by landing-page-copy); the engineering implementation; specific Stripe/Chargebee/Recurly/Paddle billing-platform configurations (those stay implementation-side).

The free-tier decision: freemium vs free-trial vs no-free

Before designing the upgrade flow, decide the free-tier structure.

Freemium (free-forever tier).

  • Users use the product indefinitely without paying.
  • Paid tier offers more value (capacity, features, support).
  • Conversion typically 2-5 percent; volume compensates.

When it works: products with strong network effects, or where free users provide product value (data, content, virality).

Free-trial (time-limited).

  • Users get full or near-full product for a defined period.
  • After trial, must pay to continue.
  • Conversion typically 10-25 percent of trial signups.

When it works: products where the value is clear quickly; audiences willing to commit time before paying.

Reverse trial.

  • Users start on paid plan; auto-downgrade to free after period.
  • Less common; mixes signals; can produce surprise churn.

No-free (paid-only).

  • No free tier; users pay to start.
  • Conversion is from prospects rather than free users.
  • Conversion rates depend on sales motion, not in-product upgrade flows.

When it works: enterprise products, high-touch sales, products where free would dilute brand or capacity.

The decision is upstream of upgrade flow design. Different free-tier structures warrant different upgrade flows.

Detail in references/free-tier-decision-criteria.md.

Paywall-everywhere vs free-forever-trap vs value-triggered-upgrade

The keystone framing.

Paywall-everywhere. Paywall blocks meaningful product use. Free tier exists but is too constrained to demonstrate value. Users churn before reaching the moment that would justify paying. Cost: users who would have paid after seeing value never reach that moment; conversion suffers despite aggressive paywalling.

Free-forever-trap. Generous free tier with no upgrade path that ever surfaces. Users get everything they need; never see why they would pay. Conversion rate stays at single-digit percentages indefinitely. Cost: the team has built a product users like for free; revenue does not follow because the upgrade ask never lands.

Value-triggered-upgrade. Paywall surfaces at moments where the user has demonstrably gotten value. The user has hit a usage threshold, completed a flow, or otherwise demonstrated they are getting the product's promise. The upgrade ask is honest about what they get next. Cost: design effort upfront is significant; conversion typically meaningfully higher than either alternative.

The litmus test. After a user encounters the upgrade flow, can they articulate why they should pay? "Because I just hit my limit on this feature I have used 200 times" is value-triggered. "Because the product told me to pay before letting me use it" is paywall-everywhere. "I have not seen an upgrade ask" is free-forever-trap.

Trigger-moment design: where paywalls earn their interruption

The single most consequential decision in upgrade flow design.

The principle. Paywalls surface at moments where the user has demonstrated they are getting the product's value. The interruption is justified because the user has a reason to say yes.

Strong trigger moments.

  • Usage threshold reached. User has used a feature N times; further use requires paid plan. Honest because they are clearly getting value.
  • Capacity limit hit. User has reached free-tier capacity; upgrade unlocks more. Predictable; expected.
  • Advanced feature attempted. User clicked into a feature that requires paid plan. Interest is fresh.
  • Workflow completed successfully. User has seen value through a completed action; upgrade ask connects that value to recurring access.
  • Team-collaboration moment. User wants to invite teammates; team capabilities require paid plan.
  • Time-trial ending. Trial-based products surface upgrade as trial nears end.

Weak trigger moments.

  • First-login. User has not yet seen value; upgrade ask is premature.
  • Random in-product placement. Paywall on the dashboard with no specific trigger; users dismiss.
  • Every-page banner. Persistent upgrade banner across all surfaces; users develop blindness.

The discipline. Each paywall should answer: what value did the user just demonstrate, and how does the paid plan extend that value?

Detail in references/trigger-moment-design.md.

Paywall presentation: modal vs banner vs inline

How the paywall surfaces.

Pattern A: Modal paywall. Full-screen overlay blocks the action; user must upgrade or dismiss.

When to use. Capacity limits, feature gates the user has hit. The interruption is warranted by the trigger.

Pattern B: Banner paywall. Persistent banner at top of page suggesting upgrade.

When to use. Soft prompts; awareness without interruption. Risk of becoming visual noise.

Pattern C: Inline paywall. Upgrade ask embedded in the surface where the trigger occurred.

When to use. Contextual prompts that integrate with the workflow.

Pattern D: Toast or notification. Brief paywall surfaced as a notification.

When to use. Soft prompts; low-priority upgrade asks.

Choice criteria.

  • The trigger's strength determines the presentation's intensity.
  • Strong triggers (capacity hit, feature gate) warrant modal.
  • Soft triggers (general awareness) warrant inline or toast.

Copy and value-prop discipline.

  • The paywall copy should connect to what the user just did.
  • "You have used [feature] 50 times. Upgrade to remove the limit and unlock [related capabilities]." matches the trigger.
  • "Upgrade for more features" is generic and weak.

Detail in references/paywall-presentation-patterns.md.

Upsell vs downsell logic

When the user does not accept the primary upgrade.

Upsell. User is on basic plan; ask them to upgrade to higher tier.

Cross-sell. User is paying; offer add-ons or related products.

Downsell. User declined the higher tier; offer a smaller commitment (smaller plan, monthly vs annual, basic vs full feature set).

The downsell discipline. Some users will not upgrade to the proposed tier but will upgrade to something. Downsell captures revenue otherwise lost.

Examples.

  • User declined Pro upgrade; offer Starter plan as a path to begin paying.
  • User declined annual plan; offer monthly with explicit cost difference disclosed.
  • User declined full team plan; offer single-seat upgrade.

Anti-pattern. Aggressive downsell that makes the user feel manipulated. Honest framing: "If Pro is more than you need, here is something that fits."

Detail in references/upsell-vs-downsell-logic.md.

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

Win-back flow design

Lapsed users, downgrades, partial-churn.

Win-back triggers.

  • User has not logged in for 30/60/90 days.
  • User downgraded plan.
  • User canceled but did not delete account.
  • User churned and signed up again later.

Win-back patterns.

  • Email-based. Outreach with renewed value-prop, sometimes with discount or trial extension.
  • In-product upon return. When the lapsed user returns, surface re-engagement help and (if appropriate) an upgrade-back ask.
  • Personal outreach. For high-value lapsed users, sales or customer success conversation.

Discount discipline.

  • Discounts to win back can create reverse-incentive (user churns to get discount).
  • Discount sparingly; emphasize new value first.

Detail in references/win-back-flow-patterns.md.

Churn prevention upstream of upgrade

The best upgrade flow is the one the user does not need because they did not churn.

Upstream churn signals.

  • Declining engagement; sessions per week dropping.
  • Last login distant.
  • Support ticket pattern (frustration signals).
  • Plan downgrade interest signals.

Prevention patterns.

  • Engagement re-orientation. Surface help when engagement drops.
  • Outreach. Customer success contact for high-value accounts at risk.
  • Friction reduction. Audit the reasons users disengage; fix the friction.

The prevention-vs-recovery economics. Preventing churn is much cheaper than winning back churned users. Invest upstream.

Detail in references/churn-prevention-upstream.md.

Plan structure: tier count, feature gating, pricing-page design

The plans that the upgrade flow leads to.

Tier count.

  • 2-tier (Free + Paid): simple; clear upgrade path; works for many products.
  • 3-tier (Starter + Pro + Enterprise): broader audience; harder to design.
  • 4+ tier: rarely better; complexity confuses users.

Feature gating.

  • Capacity-based. Free tier limited by use volume; paid unlocks more.
  • Feature-based. Free tier missing specific features; paid unlocks them.
  • Hybrid. Both capacity and features differ.

Discipline. Each tier should have a clear "this is for [X audience] because of [Y]." Tiers without clear audience-fit produce weak conversions.

Pricing-page design. The pricing page is downstream of plan structure but lives close to upgrade flow. Detail in landing-page-copy for pricing-page copy specifically.

Detail in references/plan-structure-patterns.md.

Common failure modes

Rapid-fire. Diagnoses in references/common-upgrade-failures.md.

  • "Conversion rate is low; users churn before reaching upgrade." Paywall-everywhere; gates blocking value demonstration.
  • "Conversion rate is single-digit; free users use the product for years." Free-forever-trap; no upgrade path surfaces.
  • "Paywall fires; users dismiss; conversion does not lift." Trigger moments wrong; paywall not connected to demonstrated value.
  • "Users hit paywall and churn." Wrong moment; paywall blocks before value is fresh.
  • "Upgrade rate looks fine; downgrade rate is high." Plan structure wrong; users upgrade then realize they did not need the higher tier.
  • "Win-back attempts have low conversion." Re-engagement timing wrong, or value-prop unchanged from what failed initially.
  • "Annual plans not converting; monthly plans dominate." Annual value-prop weak; or commitment friction too high.
  • "Sales says many leads come from churned users coming back." Win-back working but the previous churn was avoidable; audit upstream.
  • "Conversion did not change after we redesigned the paywall." Paywall design was not the problem; trigger or plan structure may be.

The framework: 12 considerations for upgrade flow design

When designing or auditing an upgrade flow, walk these 12 considerations.

  1. The free-tier decision. Freemium, free-trial, reverse trial, or no-free.
  2. Value-triggered-upgrade, not paywall-everywhere or free-forever-trap. Paywalls at moments of demonstrated value.
  3. Trigger-moment design sound. Paywalls connect to specific user-demonstrated value.
  4. Paywall presentation matches trigger intensity. Strong triggers warrant modal; soft triggers inline.
  5. Copy connects to the trigger. Specific value-prop tied to what the user just did.
  6. Upsell, cross-sell, downsell logic. When primary upgrade is declined, secondary paths exist.
  7. Win-back flows designed. Lapsed users have a clear re-engagement path.
  8. Churn prevention upstream. Upstream signals trigger prevention; downstream upgrade flow is one of multiple defenses.
  9. Plan structure clear. Tier count appropriate; each tier has clear audience-fit.
  10. Pricing-page coordinates with upgrade flow. Plan structure decisions reflected on the pricing page.
  11. Conversion as success metric. Not just paywall display; downstream conversion to paid.
  12. Maintenance discipline. Plans, paywalls, win-back flows updated alongside product and pricing changes.

The output of the framework is an upgrade flow that earns the user's "yes" by asking at the moment the user has a reason to say yes, with plan structure that fits the audience the product serves.

Reference files

Closing: upgrade flows earn revenue when they earn the user's yes

The upgrade flows that compound revenue are the ones that ask at the moment the user has a reason to say yes. Not because the paywall blocked them. Not because the upgrade prompt happened to appear. Because the user just did something that demonstrated value, and the upgrade ask connected that value to continued or expanded access.

That is the bar. Below the bar are paywall-everywhere (gates before value, conversion suffers) and free-forever-trap (no upgrade path, conversion never starts). Above the bar are value-triggered-upgrade flows where trigger-moment design, paywall presentation, plan structure, win-back, and churn prevention work together to convert the right users at the right moments.

The discipline is in the design choices. The free-tier decision (freemium, trial, paid-only) sets the funnel shape. Trigger-moment design decides when paywalls earn their interruption. Paywall presentation decides how the ask lands. Plan structure decides what the user is upgrading to. Win-back and churn prevention catch the cases that escaped the primary upgrade flow.

© rampstackco, 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 10 other files (references) in skills/upgrade-flow-design of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/churn-prevention-upstream.md
  • references/common-upgrade-failures.md
  • references/free-tier-decision-criteria.md
  • references/paywall-presentation-patterns.md
  • references/plan-structure-patterns.md
  • references/trigger-moment-design.md
  • references/upgrade-flow-anti-patterns.md
  • references/upsell-vs-downsell-logic.md
  • references/win-back-flow-patterns.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

Upgrade Flow Design 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.

Upgrade Flow Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Upgrade Flow Design this skillrampstackco/claude-skills935—~4.6kAutomated safety check: PassMIT
Referral Programfreekmurze/dotfiles1k16 repos~1.8kAutomated safety check: PassNone
Churn Preventionrongxinzy/RongxinAI1543 repos~2.6kAutomated safety check: PassMIT
100m Leadsgetagentseal/founder-playbook721—~2.3kAutomated safety check: PassMIT
Churn Preventionfreekmurze/dotfiles1k12 repos~4.4kAutomated safety check: PassNone
ReferralsCesarjoquin/Marketing-Skills1991 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Referral Program

    freekmurze/dotfiles

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

    1k GitHub starsUsed in 16 repos~1.8k tokens
    Marketing & SEOAuto-check passed

  • Churn Prevention

    rongxinzy/RongxinAI

    Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.

    154 GitHub starsUsed in 3 repos~2.6k tokens
    Marketing & SEOAuto-check passed

  • 100m Leads

    getagentseal/founder-playbook

    Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.

    721 GitHub stars~2.3k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Churn Prevention

    freekmurze/dotfiles

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.

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

  • Referrals

    Cesarjoquin/Marketing-Skills

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

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

  • Email Sequence Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound…

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

More from rampstackco/claude-skills

All 103 skills in this repo

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    935 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    935 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed

  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    935 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    935 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Content Strategy

    rampstackco/claude-skills

    Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

    935 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Upgrade Flow Design

What does Upgrade Flow Design do?

Designing free-to-paid conversion flows for SaaS products. An agent skill from rampstackco/claude-skills. Upgrade Flow Design is an agent skill from rampstackco/claude-skills. Designing free-to-paid conversion flows for SaaS products.

When should I use Upgrade Flow Design?

Upgrade Flow Design fits situations like: value demonstration; upsell vs downsell; churn prevention; freemium conversion.

How do I install Upgrade Flow Design in Claude Code?

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

How do I install Upgrade Flow Design in Codex?

Run `npx skills add rampstackco/claude-skills --skill upgrade-flow-design -a codex`. Or copy the skill folder (skills/upgrade-flow-design in rampstackco/claude-skills) into .agents/skills/upgrade-flow-design in your project. Codex loads it when a task matches its description.

Can I use Upgrade Flow Design 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 rampstackco/claude-skills --skill upgrade-flow-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upgrade-flow-design, .gemini/skills/upgrade-flow-design, .github/skills/upgrade-flow-design and .opencode/skills/upgrade-flow-design in your project.

What does Upgrade Flow Design need to run?

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

Does Upgrade Flow Design 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 Upgrade Flow Design 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 Upgrade Flow Design use?

Upgrade Flow Design 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 Upgrade Flow Design use?

About 4.6k tokens (SKILL.md is roughly 18k 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 16k tokens, read only when the agent opens those files.

What are the alternatives to Upgrade Flow Design?

Skills that share tags, products or a category with Upgrade Flow Design: Referral Program (freekmurze/dotfiles, 1k stars), Churn Prevention (rongxinzy/RongxinAI, 154 stars), 100m Leads (getagentseal/founder-playbook, 721 stars) and Churn Prevention (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Upgrade Flow Design?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

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