Linkly

Linkly integration. Manage Organizations, Users. Use when the user wants to interact with Linkly data.

Security Scan

The skill's instructions, dependencies, and credentials are internally consistent with a Linkly integration that uses the Membrane CLI to manage connections and run actions.

Purpose & Capability

The skill says it integrates with Linkly and all runtime instructions use the Membrane CLI and a Linkly connector key — this aligns with the stated purpose (no unrelated services or credentials are requested).

Instruction Scope

SKILL.md only instructs installing/using the Membrane CLI, creating connections, searching and running actions, and handling auth flows. It does not direct reading unrelated files, harvesting environment variables, or posting data to unexpected endpoints.

Install Mechanism

There is no automatic installer in the skill bundle, but the instructions ask the operator to run 'npm install -g @membranehq/cli@latest' (and sometimes npx). Installing an npm package is a normal step for this workflow, but global npm installs execute third-party code — users should verify the package and source before installing.

Credentials

The skill declares no required environment variables or secrets and explicitly recommends letting Membrane manage credentials. There are no disproportionate credential requests.

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes or access to other skills' configs. Runtime actions are limited to the Membrane CLI and user-driven auth flows.

Assessment

This skill is coherent: it delegates auth and API calls to the Membrane CLI rather than asking for Linkly API keys. Before installing or running the CLI, verify the @membranehq/cli package and its GitHub repository to ensure you trust the publisher. Prefer using npx or reviewing the package contents if you want to avoid a global install. When performing headless auth, only paste authorization codes into your own terminal and never share them. If you need stronger assurance, inspect Membrane's privacy/security docs and confirm the 'linkly' connector maps to the correct Linkly account and scopes.

Linkly is a smart link management platform. It's used by marketers and businesses to shorten, track, and optimize their links for better engagement and insights.

Official docs: https://developers.linkly.io/

Linkly Overview

• Link
  • Link destination
• Bundle
  • Bundle Link
• Space
• Tag
• Report

Working with Linkly

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

Use connection connect to create a new connection:

membrane connect --connectorKey linkly

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.