Agent skill · marketing growth · membranedev
wesupply
WeSupply integration. Manage data, records, and automate workflows. Use when the user wants to interact with WeSupply data.
Why this skill is useful
Adds specific commands and workflows for integrating with WeSupply that the AI wouldn't reliably generate on its own.
What it needs
Requires @membranehq/cli installed locally. Requires membrane account access. About 4k tokens when loaded. Last updated 2026-04-28. 253 stars on the source repository.
What this skill does
WeSupply WeSupply is a returns management platform that helps e-commerce businesses streamline and automate their returns process. It provides tools for customers to initiate returns, track shipments, and receive refunds or exchanges, while giving merchants visibility and control over the entire returns lifecycle. This is used by e-commerce businesses looking to improve customer satisfaction and reduce the costs associated with returns. Official docs: https://developers.wesupply.com/ WeSupply Overview Shipment Tracking Returns Inquiries Users Settings Carriers Warehouses Notifications Branding Integrations Working with WeSupply This skill uses the Membrane CLI to interact with WeSupply. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing. Install the CLI Install the Membrane CLI so you can run membrane from the terminal: Authentication This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available. Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with: Add --json to any command for machine-readable JSON output. Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness Connecting to WeSupply Use membrane connection ensure to find or create a connection by app URL or domain: The user completes authentication in the browser. The output contains the new connection id. This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically. If the returned connection has state: "READY", skip to Step 2. 1b. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills membranedev/wesupply