Sidetracker
v1.0.2Sidetracker integration. Manage Organizations, Projects, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Sidetracker data.
⭐ 0· 97·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 claims to integrate with Sidetracker and its instructions exclusively use the Membrane CLI and Membrane proxy to discover actions and call Sidetracker endpoints. No unrelated credentials, binaries, or system access are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in, creating a connection, listing actions, running actions, or proxying requests to Sidetracker. However, the Membrane request proxy allows arbitrary requests to the Sidetracker API via the connection, so the agent (or user-run commands) can issue broad API calls — expected for this integration but powerful.
Install Mechanism
There is no automated install spec in the registry; the SKILL.md recommends running `npm install -g @membranehq/cli` or using npx. Installing a global npm CLI modifies the host environment — normal for a CLI integration but worth noting. The package is from npm (traceable) rather than a raw download.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs to use Membrane's connection flow (browser-based login) rather than asking for API keys. This is proportionate, though it means you delegate credential handling to Membrane's service.
Persistence & Privilege
The skill is instruction-only, has no install-time hooks in the registry, and does not request 'always' presence or modify other skills. Agent autonomous invocation is allowed by default (platform behavior) but not unusual here.
Assessment
This skill appears to be what it says: a guide to using the Membrane CLI to interact with Sidetracker. Before installing or using it, consider: (1) You will need to install a global npm package (@membranehq/cli) — verify the package and publisher on npm and prefer using npx if you want to avoid a global install. (2) Authentication is handled via Membrane (browser login), so you are delegating access to a third‑party service — ensure you trust Membrane and review its privacy/security policies. (3) The Membrane proxy can issue arbitrary API requests on behalf of a connection, so be careful with actions that read or transmit sensitive project/user data. (4) Avoid pasting secrets into chat; prefer the documented connection flow. If you need higher assurance, verify the CLI source repository and the Membrane organization identity before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97dmq5kegzf5jffrrarehy0xd8424hn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.