Textmagic
v1.0.2TextMagic integration. Manage data, records, and automate workflows. Use when the user wants to interact with TextMagic data.
⭐ 0· 99·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description (TextMagic integration) matches the runtime instructions: discovering connectors, creating a connection, running actions, and proxying requests via the Membrane CLI. Nothing requested is unrelated to integrating with TextMagic.
Instruction Scope
SKILL.md only instructs installing/using the Membrane CLI, logging in via browser, listing/connecting to TextMagic connectors, running actions, and proxying API requests. It does not instruct reading unrelated files, asking for local secrets, or exfiltrating data to unrelated endpoints.
Install Mechanism
There is no install spec in the registry metadata, but the instructions recommend running `npm install -g @membranehq/cli` (or `npx ...`) which is a public npm package. Installing a global npm package executes third-party code on the host (normal for CLIs) — this is expected for a CLI-driven integration but carries the usual supply-chain risk of any npm package.
Credentials
The skill declares no required environment variables or credentials and explicitly directs users to create a connection via Membrane instead of supplying API keys. The only required external account is a Membrane account (and the user's TextMagic connection via Membrane), which is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill is instruction-only with no code writing to disk described. It does not request persistent system-wide privileges or modifications to other skills' configs.
Assessment
This skill is coherent with its stated purpose: it uses the Membrane CLI as a proxy to talk to TextMagic and doesn't ask for unrelated credentials. Before installing/using it: (1) confirm you trust the @membranehq/cli npm package and consider running it with npx or in a contained environment rather than a global install; (2) review Membrane's privacy/security docs because it will hold and proxy your TextMagic credentials; (3) be aware the CLI will open a browser-based login and Membrane will manage auth server-side; (4) if you allow an autonomous agent to call this skill, understand it can invoke the Membrane CLI commands described here — limit agent permissions or scope if needed.Like a lobster shell, security has layers — review code before you run it.
latestvk97ezwr5tew9dgyp6n58qqff95842e8v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.