Upkeep
v1.0.0UpKeep integration. Manage data, records, and automate workflows. Use when the user wants to interact with UpKeep data.
⭐ 0· 30·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
Name/description match the runtime instructions: the SKILL.md describes interacting with UpKeep via the Membrane CLI and shows how to discover/run actions and proxy API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating a connection to UpKeep, listing actions, running actions, and proxying API calls. They do not ask the agent to read local files, export unrelated env vars, or exfiltrate data to unknown endpoints.
Install Mechanism
No install spec in the skill bundle (instruction-only). The SKILL.md recommends installing @membranehq/cli via npm (-g), which is a normal public npm package install; consider using npx or a local install if you want to avoid global installs or elevated privileges.
Credentials
The skill requests no local env vars or credentials. However, it relies on the Membrane service/CLI to handle UpKeep authentication server-side—so using this skill involves trusting Membrane (getmembrane.com/@membranehq) to store and refresh UpKeep credentials and to proxy API requests.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent agent presence or modify other skills' configs. The usual autonomous invocation setting remains, which is expected for skills.
Assessment
This skill appears to be what it claims: an UpKeep integration that uses the Membrane CLI. Before installing, be aware that you will: (1) install or run the @membranehq/cli (npm -g or npx), (2) authenticate via a Membrane account (browser or headless flow), and (3) grant Membrane a connector to access your UpKeep data — Membrane will manage tokens server-side. If you have policy concerns, review the npm package and Membrane's privacy/security docs, consider using npx instead of a global install, and audit the connector permissions in Membrane so it only has the scopes you want. Also note that, like most skills, it can be invoked by an agent autonomously; if you prefer manual control, only call it when you intend to.Like a lobster shell, security has layers — review code before you run it.
latestvk975zpsk5btp5mm0m5twahvwk5847wqk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.