Kartra
Analysis
This appears to be a real Kartra integration, but it delegates sensitive account access to Membrane and enables broad account, billing, automation, and customer actions without clear safeguards.
Findings (10)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.
The skill makes externally returned instructions relevant to the agent's next steps without clearly saying they must be treated as untrusted or limited to the user's request.
Manage Persons, Organizations, Leads, Deals, Pipelines, Activities and more... Billing... Payments... Refunds... Webhooks... User Roles... Automations... Broadcasts
The skill covers broad and high-impact Kartra operations, including financial, messaging, webhook, automation, and access-control areas, without clear approval or containment rules.
npm install -g @membranehq/cli@latest ... If no app is found, one is created and a connector is built automatically.
The skill relies on an unpinned global npm CLI install and can trigger automatically built connector components, creating provenance and version-control gaps.
npm install -g @membranehq/cli@latest ... npx @membranehq/cli connection get <id> --wait --json
The skill requires installing and running npm-hosted CLI code. This is purpose-aligned for the integration, but it changes the local environment and executes third-party package code.
Automations... Sequences... Broadcasts... Webhooks... Billing... Payments... Refunds... User Roles... Teams
The covered Kartra areas include account-wide systems where one wrong action can propagate to customers, payment flows, webhooks, team permissions, and marketing automation.
Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
The wording is not inherently deceptive, but it may make credential delegation and persistent refresh sound routine despite the sensitivity of the access.
Membrane handles authentication and credentials refresh automatically
Automatic credential refresh indicates persistent access may remain available after setup. The artifacts do not show hidden autonomous behavior, but persistence should be noticed.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Primary credential: none ... Capability signals: requires-oauth-token; requires-sensitive-credentials
The declared credential contract conflicts with the capability signals, which indicate OAuth and sensitive credentials are required.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
`clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.
Externally supplied instructions can become part of the agent's working context and may be over-trusted if not clearly separated from user instructions.
This skill uses the Membrane CLI to interact with Kartra. Membrane handles authentication and credentials refresh automatically
The skill routes authentication and Kartra interaction through Membrane. That is disclosed and purpose-aligned, but it means credentials and account actions depend on a third-party gateway.
