Truora

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

Security Scan

The skill consistently delegates Truora access to the Membrane CLI and a Membrane account; its instructions, requirements, and behavior align with the stated purpose.

Purpose & Capability

Name and description state 'Truora integration' and all runtime instructions focus on using the Membrane CLI to connect to Truora and run actions; required capabilities are proportional to that purpose.

Instruction Scope

SKILL.md instructs the agent to install and use the Membrane CLI, perform login/connect/action-list/create/run flows, and to use browser-based authentication for credentials. It does not request unrelated file reads, unrelated environment variables, or data exfiltration steps.

Install Mechanism

There is no formal install spec in the metadata, but the README instructs users to run `npm install -g @membranehq/cli@latest` (and shows npx usage). Installing a global npm CLI is a normal way to get the tooling, but is a supply-chain risk vector — verify the package and its publisher before installing, and be aware a global npm install may require elevated privileges on some systems.

Credentials

The skill requires a Membrane account and network access (declared in the header). It requests no environment variables or secrets and explicitly advises against asking users for API keys — credential access is handled through Membrane's auth flow, which is proportionate to the integration purpose.

Persistence & Privilege

The skill is not forced-always, is user-invocable, and does not request persistent system-wide privileges or attempt to modify other skills' configs. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.

Assessment

This skill is coherent: it uses Membrane as the intermediary to access Truora. Before installing/using it, verify that @membranehq/cli and getmembrane.com are trustworthy for your environment (review the npm package and the GitHub repo if possible). Installing the CLI globally can require elevated privileges—use caution or install locally (npx) if you prefer. Understand that sensitive identity and background-check data will be accessed via Membrane, so confirm compliance with your data handling policies and that you trust Membrane to store/manage credentials. If you need further assurance, ask the publisher for the exact CLI package checksum, the repository link for the CLI package, or run the CLI in an isolated environment first.

Truora is a suite of tools focused on identity verification and fraud prevention. Businesses in Latin America use it to onboard customers securely, run background checks, and automate communication.

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

Truora Overview

• Verification
  • Callback
• List
• Campaign
  • Campaign Result
• Phone Number Intelligence
• Document
• Background Check
• Device
• User
• Organization
• Integration
• Alert
• Credit Report
• PEP and Sanction List
• Watchlist
• Driver License
• ID Card
• Passport
• Vehicle
• Health
• Address
• Company
• Shareholder
• Beneficial Owner
• Financial Statement
• Legal Representative
• Adverse Media
• Lawsuit
• Bankruptcy Proceeding
• Property
• Trademark
• Patent
• Judicial Record
• Regulatory Filing
• News Article
• Social Media Profile
• Online Review
• Blog Post
• Forum Post
• Public Record
• Sanction List Entry
• Political Exposure
• Criminal Record
• Sex Offender Registry
• Wanted Person List
• Interpol Notice
• OFAC Sanction List
• EU Sanction List
• UN Sanction List
• UK Sanction List
• Canada Sanction List
• Australia Sanction List
• New Zealand Sanction List
• Switzerland Sanction List
• Singapore Sanction List
• Hong Kong Sanction List
• Panama Sanction List
• Colombia Sanction List
• Mexico Sanction List
• Argentina Sanction List
• Brazil Sanction List
• Chile Sanction List
• Peru Sanction List
• Ecuador Sanction List
• Venezuela Sanction List
• Guatemala Sanction List
• Honduras Sanction List
• El Salvador Sanction List
• Nicaragua Sanction List
• Costa Rica Sanction List
• Dominican Republic Sanction List
• Cuba Sanction List
• Bolivia Sanction List
• Paraguay Sanction List
• Uruguay Sanction List

Working with Truora

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

Use connection connect to create a new connection:

membrane connect --connectorKey truora

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.