Tempo
v1.0.0Tempo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tempo data.
⭐ 0· 52·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 claims to integrate with Tempo and all runtime steps (install Membrane CLI, login, create a Tempo connection, run actions or proxied API requests) are directly related to that purpose. Nothing required by the SKILL.md appears unrelated to Tempo integration.
Instruction Scope
Instructions stay within the stated purpose (install CLI, authenticate, list/connect actions, run actions, proxy requests). One important operational detail: all API calls and credentials are handled through the Membrane service/CLI, so Tempo data and authentication flows will be routed to Membrane rather than only to local tooling. This is expected for this integration but worth the user's awareness.
Install Mechanism
No embedded install spec in the skill bundle; the SKILL.md instructs installing a public npm package (@membranehq/cli) globally. This is a common, proportionate installation path for a CLI-based integration. As with any npm package, there is routine supply-chain risk (public registry), but the package source is named and standard (no arbitrary downloads or extract-from-URL behavior).
Credentials
The skill declares no required env vars or credentials and the instructions rely on Membrane-managed auth (user-driven login). There are no unexpected requests for unrelated credentials. Note: the user will grant Membrane access to Tempo/Jira during connector creation, and credentials/tokens may be stored/managed by Membrane or the local CLI.
Persistence & Privilege
The skill is instruction-only, does not request always:true, and does not modify other skills or system-wide settings in the instructions. The Membrane CLI itself may persist credentials locally (typical CLI behavior), but that behavior is outside the skill bundle and is expected for a CLI integration.
Assessment
This skill is coherent: it uses the Membrane CLI to access Tempo and asks you to authenticate via Membrane rather than supply raw API keys. Before installing, verify the @membranehq/cli package source and review Membrane's privacy and access policies because your Tempo/Jira data and connector access will be routed through their service. Installing the CLI globally via npm is normal but carries standard npm supply-chain risk—use a vetted package version and consider running the install in a controlled environment. Expect the CLI to store auth tokens locally or on Membrane; the SKILL.md does not request unrelated system credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk970zm1pm0bzkw362r8jy8ht8n84b3vt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.