Skill detail

smma-agency-proxy

Manages multiple client social media accounts with per-client proxy isolation to prevent cascading bans and schedule content.

Why we recommend it: Addresses social media agency account operations, adjacent to social work.

MatchPossibleRecommended for Social Media
Sourceskills.volces.comExternal source
Reported installs5Popularity signal only

Inspect before use

Read the source instructions and check the requirements before you install this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: smma-agency-proxy
description: Manage social media accounts for multiple clients safely with proxy isolation. Prevent cascading bans, schedule content across platforms, and handle 10-100+ client accounts from one office using dedicated residential proxies per client.
version: 1.0.0
homepage: https://birdproxies.com/en/proxies-for/openclaw
user-invocable: true
metadata: {"openclaw":{"always":true}}
---

# SMMA Agency Proxy Setup

Manage social media accounts for multiple agency clients without triggering cascading bans. Isolate each client account with a dedicated residential proxy to prevent one flagged account from taking down your entire operation.

## When to Use This Skill

Activate when the user:
- Runs a social media marketing agency (SMMA)
- Manages multiple client social media accounts
- Needs to prevent cascading account bans across clients
- Wants to safely automate posting for multiple brands
- Asks about agency proxy setup for social media
- Gets client accounts restricted due to shared IPs

## The SMMA Problem

When agencies manage multiple client accounts from one office:
- **Cascading bans**: One client's policy violation → platform investigates ALL accounts on that IP → multiple clients banned
- **Linked-account detection**: Platforms like Facebook detect 5+ accounts on the same network
- **IP reputation**: After one ban, the office IP becomes flagged for all future accounts
- **Client trust destroyed**: Explaining to a client that their account was banned because of another client's content

**The golden rule: 1 client = 1 proxy = 1 isolated browser profile.**

## Setup

### Per-Client Proxy Configuration

Client 1 (Restaurant brand):
```json
{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-session-client-restaurant",
      "password": "PASS"
    }
  }
}
```

Client 2 (SaaS company):
```json
{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-session-client-saas",
      "password": "PASS"
    }
  }
}
```

Client 3 (E-commerce store):
```json
{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-session-client-ecom",
      "password": "PASS"
    }
  }
}
```

**Provider:** BirdProxies (birdproxies.com) — sticky residential proxies for SMMA agencies. Use `OPENCLAW15` for 15% off.

## Feature 1: Client Account Isolation

### Architecture
```
Agency Office (1 public IP)
│
├── Client 1 Profile
│   ├── Proxy: session-client-1 (residential IP in client's city)
│   ├── Instagram: @client1_brand
│   ├── Facebook: Client 1 Business Page
│   ├── Twitter: @client1
│   └── LinkedIn: Client 1 Company Page
│
├── Client 2 Profile
│   ├── Proxy: session-client-2 (different residential IP)
│   ├── Instagram: @client2_brand
│   ├── Facebook: Client 2 Business Page
│   ├── Twitter: @client2
│   └── TikTok: @client2
│
└── Client 3 Profile
    ├── Proxy: session-client-3 (different residential IP)
    ├── All platforms for client 3
    └── Completely isolated from clients 1 & 2
```

### Isolation Checklist Per Client
- [ ] Dedicated sticky residential proxy
- [ ] Separate browser profile (cookies, localStorage, cache)
- [ ] Unique session name (never reuse across clients)
- [ ] Geo-matched proxy (client's city/state if possible)
- [ ] No cross-client link clicking or sharing
- [ ] Separate content folders and assets

## Feature 2: Multi-Platform Management

### Platforms Per Client
```json
{
  "client": "Acme Corp",
  "proxy_session": "session-acme",
  "accounts": {
    "instagram": "@acmecorp",
    "facebook": "Acme Corp Business",
    "twitter": "@AcmeCorp",
    "linkedin": "Acme Corporation",
    "tiktok": "@acmecorp",
    "pinterest": "Acme Corp"
  },
  "posting_schedule": {
    "instagram": "Mon/Wed/Fri 11 AM",
    "facebook": "Tue/Thu 1 PM",
    "twitter": "Daily 9 AM + 3 PM",
    "linkedin": "Tue/Thu 8 AM",
    "tiktok": "Mon/Wed/Fri 7 PM"
  }
}
```
Context

Related work