Remarkety

Remarkety integration. Manage data, records, and automate workflows. Use when the user wants to interact with Remarkety data.

Security Scan

The skill's instructions, required tools, and requested access are consistent with a Remarkety integration that delegates auth and API calls to the Membrane CLI; nothing in the skill asks for unrelated secrets or system access.

Purpose & Capability

The skill declares it integrates with Remarkety and all runtime instructions show use of the Membrane CLI to authenticate, create a connection, discover actions, and run them. The requested capabilities (network access and a Membrane account) match the stated purpose.

Instruction Scope

SKILL.md restricts runtime actions to installing/using the Membrane CLI, performing login flows, creating/listing connections and actions, and running actions. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints.

Install Mechanism

There is no formal install spec in the manifest; the doc instructs users to run an npm global install (npm install -g @membranehq/cli@latest) or use npx. Installing an npm package is a normal way to obtain the CLI but carries the usual trust considerations (verify package identity and provenance).

Credentials

The skill requests no environment variables or local config paths. It explicitly advises letting Membrane manage credentials server-side and not to ask the user for API keys, which is proportionate to the integration purpose.

Persistence & Privilege

The skill does not request persistent or elevated privileges (always is false) and does not instruct modifying system-wide agent settings or other skills. It relies on an external CLI and the usual browser-based auth flow.

Assessment

This skill appears coherent, but before installing/running anything: 1) verify the Membrane project and the npm package @membranehq/cli on npmjs.org (publisher, recent versions, and repository) to ensure you trust the source; 2) prefer running the CLI yourself in a controlled environment (or container) rather than allowing automated execution; 3) follow the documented browser-based login flow and do not paste secrets into chat; 4) if you want tighter control, inspect the Membrane CLI code or run it with least privilege (avoid global installs if you prefer) and confirm that connections created are the ones you expect for your Remarkety account.

Remarkety is an email marketing platform specifically designed for e-commerce businesses. It helps online stores automate personalized email campaigns based on customer behavior and purchase history. E-commerce marketers and business owners use it to increase customer engagement and drive sales.

Official docs: https://developers.remarkety.com/

Remarkety Overview

• Campaigns
  • Campaign Email
• Contacts
• Orders
• Products
• Coupons

Use action names and parameters as needed.

Working with Remarkety

This skill uses the Membrane CLI to interact with Remarkety. 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:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

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:

membrane login complete <code>

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 Remarkety

Use connection connect to create a new connection:

membrane connect --connectorKey remarkety

The user completes authentication in the browser. The output contains the new connection id.

Listing existing connections

membrane connection list --json

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

Use npx @membranehq/cli@latest action list --intent=QUERY --connectionId=CONNECTION_ID --json to discover available actions.

Creating an action (if none exists)

If no suitable action exists, describe what you want — Membrane will build it automatically:

membrane action create "DESCRIPTION" --connectionId=CONNECTION_ID --json

The action starts in BUILDING state. Poll until it's ready:

membrane action get <id> --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

• READY — action is fully built. Proceed to running it.
• CONFIGURATION_ERROR or SETUP_FAILED — something went wrong. Check the error field for details.

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Best practices

• Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
• Discover before you build — run 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.
• Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.