agentleFS
Upload-PostUpload-Post/upload-post-plugin/skills/whitelabel-connect/SKILL.md

whitelabel-connect

Skill1 starsChanged 41 days agoMITView on GitHub

Generate a JWT-authenticated connection URL so a client or end-user can OAuth their social accounts into a profile inside YOUR Upload-Post workspace. For white-label integrations, SaaS embeds and agency client onboarding. NOT for connecting your own accounts — for that, send the user to https://app.upload-post.com/manage-users in their browser.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you operate a SaaS, agency or platform that wants end-users (your clients) to connect their social accounts to a …

    line 8
  2. Distinctive:

    If the user wants to connect their own social accounts to their own Upload-Post workspace, stop.

    line 12
  3. Distinctive:

    Create a profile, click the platform, accept the OAuth prompt.

    line 18
  4. Very specific:

    Call list_users and inspect the client's profile in social_accounts.

    line 50
  5. Very specific:

    If you are onboarding many clients at once, batch the calls: one create_user + one generate_jwt per client.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Generate a white-label connection link

Use this skill when you operate a SaaS, agency or platform that wants end-users (your clients) to connect their social accounts to a profile inside your Upload-Post workspace. They run the OAuth themselves; the connected account ends up under a profile you administer.

When NOT to use this

If the user wants to connect their own social accounts to their own Upload-Post workspace, stop. They do not need a JWT flow. Direct them to:

https://app.upload-post.com/manage-users

Create a profile, click the platform, accept the OAuth prompt. A couple of clicks per network and they're connected. Faster, no code, no link to pass around.

When to use this

  • You run an agency and want each client to connect their own Instagram / TikTok / YouTube to a profile inside your account.
  • You have a SaaS product embedding Upload-Post and need to hand users a connection URL.
  • You are onboarding a partner who should never see your API key.

Workflow

1. Pick or create the profile

Each connected account belongs to a profile (a username value inside your workspace). If the client does not have a profile yet, create one with create_user. Tell them this is the bucket their connected accounts will live in.

2. Generate the URL

Call generate_jwt with:

  • username — the profile name (the bucket).
  • platforms — array of platforms the user should be allowed to connect; defaults to all.
  • redirectUrl — where to send the client after they finish OAuth.
  • Optional: logoImage, connectTitle, connectDescription — branded copy on the connect page.
  • Optional: showCalendar, readonlyCalendar — embed the scheduler view too.

The tool returns a one-time URL.

3. Hand the URL to the client

Pass the link by email, Slack, in your product UI — however you onboard. They open it, pick the platform, complete the platform's native OAuth, and end up at your redirectUrl.

4. Verify

Call list_users and inspect the client's profile in social_accounts. The platform should have a non-empty entry with handle and display_name. If reauth_required: true shows up later, the token expired — generate a fresh JWT URL and resend.

Bulk onboarding

If you are onboarding many clients at once, batch the calls: one create_user + one generate_jwt per client. Store the URLs in your own system and send them out. There is no built-in mass-mailer in Upload-Post — that is on your side.

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.