Modeck
v1.0.0MoDeck integration. Manage data, records, and automate workflows. Use when the user wants to interact with MoDeck data.
⭐ 0· 26·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
medium confidencePurpose & Capability
The skill's name/description (MoDeck integration) matches the instructions: it tells the agent to use the Membrane CLI to connect, list, and run actions against MoDeck. Asking for the Membrane CLI and a Membrane account is proportional to the stated purpose.
Instruction Scope
SKILL.md stays within scope: it instructs installing the Membrane CLI, performing login, creating connections, listing/running actions, and using a proxy request. It does not instruct reading unrelated files or exporting secrets. Minor documentation inconsistencies exist (an 'Official docs' link points to Twitter's developer docs, and the doc mixes the names 'MoDeck' and 'Membrane'), which may be copy/paste errors that warrant verification.
Install Mechanism
No install spec is embedded (instruction-only). The doc recommends installing @membranehq/cli via 'npm install -g', which is a standard package install approach but will write a global binary — verify the package name and publisher on npm before running global installs.
Credentials
The skill declares no required environment variables, secrets, or config paths. Its instructions explicitly tell users not to provide API keys and to rely on Membrane for auth, which is proportional to its function.
Persistence & Privilege
Skill is instruction-only, has no install-time hooks, and 'always' is false. It does not request permanent system presence or modifications to other skills or system-wide settings.
Assessment
This skill is primarily documentation for using the Membrane CLI to access MoDeck and does not itself request secrets or install code. Before using it: 1) Verify you trust getmembrane.com and the @membranehq/cli npm package (check the npm publisher, package README, and repository). 2) Avoid running unfamiliar global npm installs without review. 3) Confirm the connector/action IDs and responses in a safe/test account before automating writes. 4) Note the doc has small copy/paste errors (e.g., a Twitter docs link) — if anything looks inconsistent with your expected MoDeck API, double-check the official Membrane/MoDeck documentation or the referenced repository. If you need higher assurance, ask the skill author for a pointer to the exact npm package and its source repo or verify the package on npm/github yourself.Like a lobster shell, security has layers — review code before you run it.
latestvk971mh1cxafhmrs4kg8stbthcx848rf9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.