Adversus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adversus data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adversus60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Adversus is a competitive intelligence platform. It helps businesses monitor and analyze their competitors' strategies, marketing efforts, and overall market presence. This allows product managers and marketing teams to make data-driven decisions.
Official docs: https://www.adversus.io/api-documentation
Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Adversus. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/climembrane login --tenantA browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search adversus --elementType=connector --jsonoutput.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --jsonWhen you are not sure if connection already exists:
membrane connection list --jsonconnectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --jsonThis will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| Add Activity to Lead | add-activity-to-lead | Add an activity to a lead in Adversus |
| Add Note to Lead | add-note-to-lead | Add a note to a lead in Adversus |
| Assign Lead to Campaign | assign-lead-to-campaign | Assign a lead to a campaign in Adversus |
| Change Lead Status | change-lead-status | Change the status of a lead in Adversus |
| Get Lead | get-lead | Retrieve a lead by ID from Adversus |
| Update Lead | update-lead | Update an existing lead in Adversus |
| Create Lead | create-lead | Create a new lead in Adversus |
| List Campaigns | list-campaigns | Retrieve a list of campaigns for the authenticated user |
| Get Organization | get-organization | Retrieve organization details for the authenticated user |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --jsonTo pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"When the available actions don't cover your use case, you can send requests directly to the Adversus API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpointCommon options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.