Quiz Funnel Analyzer for Competitive Intelligence

VerifiedCaution

Automatically navigates through quiz funnels for competitive intelligence, capturing every screen and generating a comprehensive analysis report covering structure, personalization, paywall tactics, and strengths/weaknesses. Helps in understanding competitors' quiz strategies and identifying psychological and conversion tactics.

Sby Skills Guide Bot
Data & AIIntermediate
406/2/2026
Claude Code
#quiz-funnel-analysis#competitive-intelligence#personalization-analysis#paywall-analysis

Recommended for

Our review

This skill analyzes a quiz funnel for competitive intelligence by navigating through every screen and generating a comprehensive report covering structure, personalization, paywall, and psychological tactics.

Strengths

  • Systematically captures the entire user flow of a quiz
  • Provides deep analysis of personalization and monetization strategies
  • Identifies psychological tactics used throughout the funnel

Limitations

  • Requires manual review of screenshots for certain details
  • May fail on quizzes with heavy client-side logic or CAPTCHAs
  • Does not handle quizzes that require prior authentication
When to use it

Use this skill when you need to reverse-engineer a competitor's quiz funnel for competitive intelligence and understand their conversion strategies.

When not to use it

Do not use this skill if the quiz relies heavily on client-side encryption or if you need a real-time analysis without screenshot capture.

Security analysis

Caution
Quality score90/100

The skill instructs browser navigation, screenshot capture, and local file writing for competitive analysis. It does not exfiltrate data, execute remote scripts, or disable safety. However, the use of browser automation and Bash on user-provided URLs introduces risk if the user supplies malicious URLs. Overall, it is legitimate but powerful.

Findings
  • Uses browser automation tools to navigate arbitrary user-provided URLs, which could potentially access malicious sites.
  • Uses Bash to create directories and write files locally, but no exfiltration or network calls to external servers.
  • No explicit destructive commands, but the combination of powerful tools warrants caution.

Examples

Analyze a competitor quiz
/analyze-quiz https://example.com/quiz
Analyze with custom name
/analyze-quiz https://example.com/quiz --name CompetitorName

name: analyze-quiz description: Analyze quiz funnels for competitive intelligence. Navigates through entire quiz, captures every screen, and generates comprehensive analysis report with structure, personalization, paywall analysis, and strengths/weaknesses.

Usage

/analyze-quiz <quiz-url>
/analyze-quiz <quiz-url> --name "CompanyName"

Instructions

You are analyzing a quiz funnel for competitive intelligence. Follow this process exactly.

Phase 1: Setup

  1. Extract company name from URL or --name parameter (default to domain name)
  2. Create timestamp: YYYY-MM-DD-HHmm
  3. Create output directory using Bash:
    mkdir -p ~/Downloads/quiz-analysis-[name]-[timestamp]
    
  4. Initialize a working notes variable to track screen data

Phase 2: Quiz Navigation

Navigate to the quiz URL using browser_navigate.

For each screen, repeat until you reach the paywall/final offer:

  1. Capture screenshot:

    browser_take_screenshot with filename: ~/Downloads/quiz-analysis-[name]-[timestamp]/[##]-[screen-type].png
    

    Use sequential numbering: 01, 02, 03... Screen types: landing, question, email-capture, loading, results, paywall, upsell

  2. Capture accessibility snapshot:

    browser_snapshot
    

    Extract: question text, answer options, button labels, progress indicators

  3. Record screen data in your working notes:

    • Screen number
    • Question/content
    • Answer options (if any)
    • Question type (multiple choice, slider, text input, etc.)
    • UI elements noted
  4. Handle special inputs:

    • Email field → type test@example.com
    • Name field → type Test User
    • Phone field → type 555-0100
    • Age/number fields → use reasonable values (30, etc.)
  5. Navigate to next screen: Look for CTA buttons in this priority order:

    • Explicit: "Next", "Continue", "Get Started", "Start Quiz", "Get Results", "See Results"
    • Arrows: "→", "❯", right-arrow icons
    • Submit buttons on forms
    • Any prominent button that advances the flow

    Use browser_click on the identified element.

  6. Wait for page transition: Use browser_wait_for with time: 1-2 seconds for animations

  7. Detect endpoint: Stop navigation when you see:

    • Pricing/payment information
    • Checkout form
    • "Subscribe", "Buy", "Purchase" CTAs
    • Plan comparison tables
    • Credit card input fields

Phase 3: Analysis

After capturing all screens, analyze your collected data:

A. Quiz Structure

  • Total number of screens
  • Number of actual questions vs informational screens
  • Question types used (list them)
  • Progress indicator style (percentage, steps, bar, none)
  • Estimated completion time
  • Any branching/personalization indicators

B. Screen-by-Screen Summary Create a table: | # | Screenshot | Type | Content Summary | Options/Input | Notes | |---|------------|------|-----------------|---------------|-------|

C. Personalization Analysis

  • What personal data is collected (list all fields)
  • How is personalization promised to the user?
  • "Calculating/analyzing" screen tactics (what do they show?)
  • How does the results/offer page use collected data?
  • Personalized copy patterns observed

D. Paywall/Offer Analysis

  • Pricing structure (plans, prices, durations)
  • Price anchoring tactics (crossed out prices, "was/now")
  • Urgency/scarcity elements (timers, limited spots, etc.)
  • Trial offers (free trial, money-back guarantee)
  • Social proof on paywall (testimonials, user count, ratings)
  • Trust signals (guarantees, security badges, payment icons)
  • CTA button copy and design
  • Multiple payment options shown?
  • Upsells or downsells present?

E. Psychological Tactics Identified

  • Commitment/consistency (small yeses leading to big yes)
  • Social proof usage (where and how)
  • Authority signals (experts, certifications, press logos)
  • Scarcity/urgency (real or artificial)
  • Loss aversion triggers
  • Personalization/relevance hooks
  • Sunk cost indicators (progress bars, time invested)

F. Key Strengths List 5-10 things they do well:

  • Strong UX patterns
  • Clever copy techniques
  • Effective design choices
  • Smart psychological triggers
  • Worth adopting for your own quizzes

G. Key Weaknesses List 5-10 improvement opportunities:

  • Friction points in the flow
  • Missing trust elements
  • Confusing or unclear screens
  • Weak paywall elements
  • Poor mobile considerations
  • Missed personalization opportunities

Phase 4: Report Generation

Write the final markdown report to ~/Downloads/quiz-analysis-[name]-[timestamp].md:

# Quiz Funnel Analysis: [Company Name]

**URL:** [quiz-url]
**Analyzed:** [date]
**Total Screens:** [count]

## Executive Summary

[2-3 paragraph overview of the quiz, its approach, and key findings]

## Quiz Structure

[Section A findings]

## Screen-by-Screen Breakdown

[Section B table with screenshot references like ![Screen 1](./quiz-analysis-[name]-[timestamp]/01-landing.png)]

## Personalization Strategy

[Section C findings]

## Paywall & Offer Analysis

[Section D findings]

## Psychological Tactics

[Section E findings]

## Strengths

[Section F as bullet points]

## Weaknesses & Opportunities

[Section G as bullet points]

## Key Takeaways

[3-5 actionable insights for competitive advantage]

Output Confirmation

After generating the report, confirm to the user:

  • Report location: ~/Downloads/quiz-analysis-[name]-[timestamp].md
  • Screenshots folder: ~/Downloads/quiz-analysis-[name]-[timestamp]/
  • Number of screens captured
  • Brief summary of key findings

Error Handling

  • If quiz requires account/login: Stop and report, note what screens were captured
  • If quiz has CAPTCHA: Stop and report
  • If navigation gets stuck: Try alternative button selectors, report if still stuck
  • If paywall requires payment to continue: Stop at paywall (expected behavior)

Tips

  • Some quizzes have loading/animation screens - wait for them to complete
  • Watch for A/B test indicators in URLs (variant=, ab=, etc.) and note them
  • If options seem to branch the quiz, note which path was taken
  • Capture any exit-intent popups or special offers that appear
Related skills