Chatwork
v1.0.2Chatwork integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatwork data.
⭐ 0· 121·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Chatwork integration) matches the instructions (use Membrane CLI to create connections, list actions, run API requests). No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent to install and use the Membrane CLI, run commands to create connections and proxy requests to the Chatwork API. It does not instruct reading unrelated files, collecting system secrets, or sending data to unexpected endpoints. The proxy capability is explicitly to Chatwork via Membrane, which is consistent with the stated purpose.
Install Mechanism
There is no formal install spec in the registry — the doc tells users to run `npm install -g @membranehq/cli`. Installing an npm global package is a standard way to obtain a CLI, but it executes third‑party code on the machine. This is expected for a CLI-based integration but carries the usual risks of running unreviewed npm packages.
Credentials
The skill declares no required env vars, no config paths, and no primary credential. The instructions explicitly advise letting Membrane handle credentials rather than asking for API keys, which is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-on and does not request persistent platform privileges. It does not modify other skills or system-wide settings according to the provided instructions.
Assessment
This skill appears to do what it claims: it relies on the Membrane CLI to handle authentication and proxy Chatwork API calls. Before installing, verify the @membranehq/cli package is the official package (check the npm page, maintainers, and repository), and consider installing it in a controlled environment (container, VM, or using npx) rather than globally if you’re cautious. Review Membrane’s privacy/security documentation because authenticating a connector will allow Membrane to access Chatwork data on your behalf. Do not supply Chatwork API keys directly to the skill — follow the connector flow described instead.Like a lobster shell, security has layers — review code before you run it.
latestvk974cyttz0kpk7r8xbzv7mrrqd8421fw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.