Timing
v1.0.0Timing integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timing data.
⭐ 0· 58·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 claim a Timing integration and the SKILL.md consistently instructs the agent to use the Membrane CLI to connect to Timing, list actions, run actions, and proxy API requests. No unrelated services, environment variables, or unusual binaries are requested.
Instruction Scope
Runtime instructions are focused on installing/using the Membrane CLI, logging in, creating/choosing a Timing connection, discovering actions, running actions, and proxying requests. There are no instructions to read unrelated files, export local credentials, or transmit arbitrary system data.
Install Mechanism
The skill is instruction-only (no install spec), but the SKILL.md tells the user to install @membranehq/cli via npm (npm install -g) and uses npx in examples. Installing an npm CLI from the public registry is a reasonable approach for this integration, but it is an extra step that installs code on the user's machine; users should confirm they trust @membranehq/cli and prefer audited installs when possible.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The instructions explicitly advise letting Membrane manage credentials and not to collect API keys locally. Note: the user must authenticate to Membrane and authorize access to their Timing account, which is expected for this integration.
Persistence & Privilege
The skill does not request persistent platform privileges (always:false). There is no indication it modifies other skills or system-wide settings. Autonomous invocation is allowed (default) but this is typical and not combined with other concerning privileges.
Assessment
This skill is coherent with a Timing integration that uses Membrane. Before installing/using it: verify you trust the @membranehq/cli npm package and the Membrane service (review their homepage/repository and privacy policy); be prepared to authenticate via browser and grant Membrane access to your Timing account (this gives Membrane access to your Timing data); prefer installing from an audited package manager or using a container if you have security concerns about global npm installs; never paste Timing or other API keys into chat—use the connection flow described instead.Like a lobster shell, security has layers — review code before you run it.
latestvk9760nfad5satnbkwhzjv4adhn848skx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.