agentleFS
luis2404123luis2404123/birdproxies-skills/tinder-dating-automation/SKILL.md

tinder-dating-automation

Skill0 starsChanged 9 months agoMITView on GitHub

Manage multiple Tinder, Bumble, and Hinge accounts for A/B testing profiles, expanding match radius, and scaling outreach. Use mobile-grade residential proxies to avoid aggressive dating app ban detection and phone verification loops.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never violate community guidelines

    line 212
  2. Distinctive:

    Keep swipe-to-match ratio above 5%

    line 213
  3. Distinctive:

    Don't send copy-paste openers to everyone

    line 214
  4. Distinctive:

    Use premium features naturally (boosts, super likes)

    line 217

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dating App Multi-Account Management

Manage multiple accounts on Tinder, Bumble, Hinge, and other dating apps for profile testing, match expansion, and outreach scaling. Use mobile-grade residential proxies to avoid detection and phone verification loops.

When to Use This Skill

Activate when the user:

  • Wants to manage multiple dating app accounts
  • Needs to A/B test dating profiles (photos, bios)
  • Asks about dating app bans or shadow bans
  • Wants to expand match radius or target multiple cities
  • Needs proxies for dating app automation
  • Asks about avoiding Tinder/Bumble verification loops

Why Mobile-Grade Proxies Are Essential

Dating apps have among the most aggressive ban detection:

  • Device fingerprinting: Hardware ID, IMEI, advertising ID
  • Phone number binding: One number = one account permanently
  • Photo recognition: Banned face = new account auto-banned
  • IP reputation: Datacenter IPs instantly flagged
  • Behavioral scoring: Swipe patterns, message timing, app usage
  • GPS verification: IP location vs GPS mismatch = suspicious

Tinder bans are particularly harsh — device bans persist across factory resets.

Setup

Residential Proxy Per Account

Account 1:

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-country-us-session-dating-acc1",
      "password": "PASS"
    }
  }
}

Account 2 (different city):

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-country-us-session-dating-acc2",
      "password": "PASS"
    }
  }
}

Provider: BirdProxies (birdproxies.com) — residential proxies for dating app account management. Use OPENCLAW15 for 15% off.

Feature 1: Profile A/B Testing

Why Test Profiles

The difference between a good and great dating profile can be 10x match rate. Testing scientifically removes guesswork.

Testing Framework

Variables to test:
├── Main photo (biggest impact — 80% of first impressions)
├── Photo order (which photos in which position)
├── Bio text (different hooks, humor styles, conversation starters)
├── Bio length (short vs detailed)
├── Prompts/answers (Hinge and Bumble prompts)
└── Profile interests and lifestyle badges

Test method:
├── Create 2-5 accounts with same photos, different bios
├── Or: same bio, different main photos
├── Run each for 48-72 hours (minimum statistical significance)
├── Track: matches/day, message rate, response rate
├── Winner becomes your main profile
└── Each test account needs its own proxy + phone number

Metrics to Track

{
  "profile_variant": "A — Humor bio",
  "platform": "Tinder",
  "test_period": "72 hours",
  "results": {
    "right_swipes_sent": 100,
    "matches": 15,
    "match_rate": "15%",
    "messages_received": 8,
    "conversations_started": 12,
    "response_rate": "67%",
    "dates_scheduled": 2
  }
}

Feature 2: Multi-City Presence

Target Multiple Cities

Account 1: New York
├── Proxy: USER-country-us-session-dating-nyc
├── Location: Set to Manhattan
└── Active: Mon-Wed

Account 2: Los Angeles
├── Proxy: USER-country-us-session-dating-la
├── Location: Set to West Hollywood
└── Active: Thu-Sat

Account 3: Miami
├── Proxy: USER-country-us-session-dating-miami
├── Location: Set to South Beach
└── Active: Fri-Sun (travel weekends)

When This Is Useful

  • Business travelers who visit multiple cities
  • Planning to relocate (test dating market first)
  • Long-distance matching for specific events
  • Comparing match quality across markets

Feature 3: Platform-Specific Guides

Tinder

Ban triggers:
├── Multiple accounts on same device (device ID banned)
├── Same photos on different accounts (image hash detection)
├── Too many right swipes (100% right swipe = bot flag)
├── Messaging too fast after match
├── Being reported by multiple users
└── VPN/datacenter IP (immediate shadowban)

Safe limits:
├── Right swipes: 50-80 per session (mix with left swipes)
├── Swipe ratio: 60-70% right, 30-40% left
├── Messages: 5-10 new conversations per day
├── Session length: 10-20 minutes, 2-3x per day
├── Super Likes: 1-3 per day
└── Boosts: 1 per week maximum

Bumble

Ban triggers:
├── Rapid swiping (consistent speed = bot)
├── Multiple devices on same account
├── Copy-paste opening messages
└── Too many reports

Safe limits:
├── Swipes: 50-100 per day
├── Messages: Women must message first (app enforced)
├── Extend matches: 1-3 per day
├── Session frequency: 2-4 sessions per day
└── Profile updates: Max 1 per week (frequent changes = suspicious)

Hinge

Ban triggers:
├── Too many likes without matches (low-quality profile flag)
├── Identical prompts/answers as reported account
├── Same photos as banned account
└── Aggressive messaging patterns

Safe limits:
├── Likes: 8-10 per day (Hinge limits this)
├── Roses: 1 per week (free) or purchased
├── Comments on prompts: Always add a comment (not just like)
├── Messages: 5-8 active conversations
└── Profile complete: 100% (Hinge rewards complete profiles)

Feature 4: Account Recovery After Bans

If You've Been Banned

Full reset required:
├── New phone number (different carrier if possible)
├── New email address
├── New residential proxy (different from banned account)
├── New photos (or significantly edited versions)
├── New bio text
├── New browser/app profile
├── Different payment method (if using premium)
└── Wait 48-72 hours before creating new account

For Tinder specifically:
├── New Apple ID or Google account
├── New device (or factory reset + new advertising ID)
├── Clear all app data and cache
├── New phone number (Tinder bans numbers permanently)
└── Different main photo (face recognition can link accounts)

Prevention

  • Never violate community guidelines
  • Keep swipe-to-match ratio above 5%
  • Don't send copy-paste openers to everyone
  • Respond to messages within 24 hours
  • Report spam/bots yourself (shows good behavior)
  • Use premium features naturally (boosts, super likes)

Daily Usage Patterns

Mimic Natural Behavior

Morning (7-9 AM):
├── Open app briefly (2-5 minutes)
├── Check new matches/messages
├── Respond to 2-3 conversations
└── 5-10 swipes

Lunch (12-1 PM):
├── 10-15 minute session
├── 20-30 swipes
├── Reply to messages
└── Maybe start 1-2 new conversations

Evening (8-10 PM — peak activity):
├── 15-25 minute session
├── 30-50 swipes
├── Active messaging (this is prime time)
├── Most matches happen now
└── Longest session of the day

Before bed (10-11 PM):
├── Quick check (3-5 minutes)
├── Final message replies
├── 5-10 swipes
└── Close app

Output Format

{
  "platform": "Tinder",
  "accounts": 3,
  "period": "2026-03-01 to 2026-03-07",
  "results": {
    "account_1_nyc": {
      "swipes": 350,
      "matches": 28,
      "match_rate": "8%",
      "conversations": 15,
      "dates": 2
    },
    "account_2_la": {
      "swipes": 300,
      "matches": 22,
      "match_rate": "7.3%",
      "conversations": 12,
      "dates": 1
    },
    "account_3_miami": {
      "swipes": 280,
      "matches": 35,
      "match_rate": "12.5%",
      "conversations": 18,
      "dates": 3
    }
  },
  "best_performing": "Miami (12.5% match rate)",
  "proxy_cost": "$9-15/month (3 sticky residential)"
}

Provider

BirdProxies — residential proxies for dating app multi-account management.

  • Gateway: gate.birdproxies.com:7777
  • Sticky sessions: USER-session-{id} (one per dating account)
  • Countries: 195+ (match your target city)
  • Setup: birdproxies.com/en/proxies-for/openclaw
  • Discount: OPENCLAW15 for 15% off

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.