Skip to content
skillsafebeta
← Report library
Purpose / Other

Paywalls Skill Security Audit

What the author says it does (original text)

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 conve

Independent security check

Security risks found

Files checked
3
Risks found
3
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 1
Medium risk

Personalization experiments may expand behavioral-data collection and use

Source references: 2
What we found

The experiment list recommends tailoring paywalls from features used, usage statistics, behavior patterns, segments, roles, and traffic sources, without requiring minimization, notice, consent, retention limits, or safeguards against sensitive inference.

Why this matters

If implemented, behavioral telemetry could become profiling and sales targeting beyond what users expect. Role, industry, or acquisition-source segmentation could also produce materially different commercial treatment.

What this evidence establishes

The list recommends personalization using feature usage, statistics, behavior patterns, segments, roles, and traffic sources. If implemented, this could broaden use of behavioral data and affect which pricing or persuasion users see. However, these are experiment ideas and do not explicitly require new collection, sensitive-data linkage, or data upload, so the actual privacy impact is unclear. Users can ask what existing data is used, whether consent is required, and whether personalization can be disabled.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
references/experiments.md:134In the instructionsOpen original file
### Usage-Based- Personalize paywall copy based on features used- Highlight most-used premium features- Show usage stats ("You've created 50 projects")- Recommend plan based on behavior patterns- Dynamic feature emphasis based on user segment
Show 1 other places
references/experiments.md:141In the instructionsOpen original file
### Segment-Specific- Different paywall for power users vs. casual users- B2B vs. B2C messaging variations- Industry-specific value propositions- Role-based feature highlighting- Traffic source-based messaging
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.Risks found: 1
Medium risk

Repository marketing files can influence the agent without a trust check

Source references: 1
What we found

The Skill tells the agent to automatically read several hidden or legacy marketing-context files and “use that context,” but does not say to treat their contents only as data or reject instructions embedded in them.

Why this matters

If such a file was supplied by an untrusted template, dependency, or collaborator, prompt-injection text could redirect recommendations, induce additional file access, or distort the user's decisions. The evidence does not show that this has occurred.

The Skill actively reads project marketing context and directly uses it before making recommendations. If a third party, template, or untrusted contributor controls those files, instructions disguised as context could influence the agent's advice or later actions; the Skill does not say to ignore operational instructions inside them. Users can ask the author to treat them only as factual data and disclose sensitive inputs for confirmation.

SKILL.md:15In the instructionsOpen original file
**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.
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

Some experiments could become deceptive urgency or accidental subscription paths

Source references: 5
What we found

The experiment list proposes limited-time countdowns, “Don't lose your work” messaging, last-chance offers, card-required trials, one-click upgrades, and escalating urgency. Although the main guide discourages pressure, these experiments do not require genuine deadlines, prominent renewal terms, or final purchase confirmation.

Why this matters

If implemented aggressively, users could make rushed purchases because of false scarcity or fear of loss, or enter paid renewals without clearly understanding the charge.

The experiments actively suggest countdown offers, loss/urgency messaging, card-required trials, one-click upgrades, and escalating urgency. If deadlines are artificial, renewal terms are inconspicuous, or upgrades lack confirmation, users could buy under pressure or subscribe unintentionally. The main guide separately says not to pressure users and to allow free continuation, so these are not unconditional directives, but those safeguards are not attached to the specific tests. Users can require genuine deadlines, prominent price/renewal disclosure, and explicit confirmation before charging.

references/experiments.md:73In the instructionsOpen original file
### Discounts & Offers- First month/year discount for conversion- Limited-time upgrade offer with countdown- Loyalty discount based on free usage duration- Bundle discount for annual commitment- Referral discount for social proof
Show 4 other places
references/experiments.md:84In the instructionsOpen original file
### Headlines- Benefit-focused ("Unlock unlimited projects") vs. feature-focused ("Get Pro features")- Question format ("Ready to do more?") vs. statement format- Urgency-based ("Don't lose your work") vs. value-based- Personalized headline with user's name or usage data- Social proof headline ("Join 10,000+ Pro users")
references/experiments.md:109In the instructionsOpen original file
### Trial Structure- 7-day vs. 14-day vs. 30-day trial length- Credit card required vs. not required for trial- Full-access trial vs. limited feature trial- Trial extension offer for engaged users- Second trial offer for expired/churned users### Trial Expiration- Countdown timer visibility (always vs. near end)- Email reminders: frequency and timing- Grace period after expiration vs. immediate downgrade- "Last chance" offer with discount- Pause option vs. immediate cancellation### Upgrade Path- One-click upgrade from paywall vs. separate checkout- Pre-filled payment info for returning users- Multiple payment methods offered
references/experiments.md:116In the instructionsOpen original file
### Trial Expiration- Countdown timer visibility (always vs. near end)- Email reminders: frequency and timing- Grace period after expiration vs. immediate downgrade- "Last chance" offer with discount- Pause option vs. immediate cancellation### Upgrade Path- One-click upgrade from paywall vs. separate checkout- Pre-filled payment info for returning users
SKILL.md:43In the instructionsOpen original file
### 4. Respect the No- Don't trap or pressure- Make it easy to continue free- Maintain trust for future conversion

Inside this skill

8 instruction sections

This Skill is an advisory guide for in-app paywalls, intended to convert free users to paid or higher-tier plans. The supplied source contains no executable scripts, installation commands, or network calls.

View source
SKILL.md:10In the instructionsOpen original file
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.

It directs the agent to read product-marketing documents in the project and use their contents when forming recommendations and questions.

View source
SKILL.md:14In the instructionsOpen original file
**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.

The core guide explicitly calls for a free or later escape path and warns against hidden close controls, confusing plan selection, and guilt-based copy.

View source
SKILL.md:43In the instructionsOpen original file
### 4. Respect the No- Don't trap or pressure- Make it easy to continue free- Maintain trust for future conversion
SKILL.md:198In the instructionsOpen original file
### Dark Patterns- Hiding the close button- Confusing plan selection- Guilt-trip copy

The accompanying experiment list proposes personalizing paywalls using usage, behavior, role, and traffic-source information.

View source
references/experiments.md:134In the instructionsOpen original file
### Usage-Based- Personalize paywall copy based on features used- Highlight most-used premium features- Show usage stats ("You've created 50 projects")- Recommend plan based on behavior patterns- Dynamic feature emphasis based on user segment
references/experiments.md:141In the instructionsOpen original file
### Segment-Specific- Different paywall for power users vs. casual users- B2B vs. B2C messaging variations- Industry-specific value propositions- Role-based feature highlighting- Traffic source-based messaging
Start here · InstructionsSKILL.md
paywalls
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source. 3 more sections are available in the original file.

File reference map

References: 1
Files making referencesReferenced content
Lines show actual file references, not execution order. Select a node to highlight its connections and inspect the files and source locations. Dashed lines include files that still need locating.
Files and check records3 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included
  • references/experiments.mdFull text included
  • evals/evals.jsonFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
  • evals/evals.jsonSupporting file
  • references/experiments.mdSupporting file
Lines read
487
File checksum (to compare versions)
35b27380af75c2e35ddbf53e78e8b39a786c21ae9b532d62cbd55bf4a678ee1a