Teamdeck
v1.0.2Teamdeck integration. Manage Organizations. Use when the user wants to interact with Teamdeck data.
⭐ 0· 113·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 (Teamdeck integration) aligns with the instructions (use Membrane to access Teamdeck). Minor inconsistency: registry metadata lists no required binaries or credentials, but SKILL.md instructs installing and using the @membranehq/cli and requires a Membrane account and network access.
Instruction Scope
Runtime instructions are scoped to using the Membrane CLI (action list/run, connection creation, and proxying requests) and browser-based auth; they do not request reading unrelated system files, environment variables, or other credentials.
Install Mechanism
There is no automated install spec in the registry (the skill is instruction-only). SKILL.md recommends installing the Membrane CLI via 'npm install -g @membranehq/cli' (a public npm package). This is expected for this integration but is an install step the user must perform; installing global npm packages has the usual supply-chain considerations.
Credentials
The skill does not declare or require additional environment variables or unrelated credentials. It relies on Membrane for authentication and OAuth-style browser flows, which is proportionate for a third-party API integration.
Persistence & Privilege
Skill is instruction-only, has always:false, and does not request persistent elevated privileges or access to other skills' configs.
Assessment
This is an instruction-only Teamdeck integration that uses the Membrane CLI as a proxy for API calls. Before installing or using it: (1) verify the @membranehq CLI package and vendor (review package page, GitHub repo, and permissions); (2) understand that authorizing a connection requires browser/OAuth consent and grants Membrane access to your Teamdeck data—review the scopes and privacy policy; (3) prefer using npx or a non-global install if you don’t want a global npm package; (4) run CLI installs in a controlled environment (not as root) and audit network access; (5) note the registry metadata did not list the Membrane CLI or a Membrane account requirement—make sure you’re comfortable performing those manual steps. There are no scan findings (the skill is instruction-only), but installing third-party CLIs and granting OAuth access are the main risks to review.Like a lobster shell, security has layers — review code before you run it.
latestvk97dgvg2qnqja4hh783t63y7t9843rbj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.