Timetastic
v1.0.0Timetastic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timetastic data.
⭐ 0· 49·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 name/description state a Timetastic integration and the SKILL.md exclusively instructs use of the Membrane CLI to access Timetastic. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
Instructions are scoped to installing and using the @membranehq/cli (login, create connection, list/run actions, proxy requests). They do not ask the agent to read local files or unrelated credentials. However, the SKILL.md relies on Membrane's proxying of API calls, which means user Timetastic data and auth flows will transit through Membrane's service — a privacy/trust consideration.
Install Mechanism
No install spec in the skill bundle itself, but the instructions require running `npm install -g @membranehq/cli`. Installing a global npm package from the public registry is expected for a CLI integration but carries the usual supply-chain risk of executing third-party code; verify package provenance and review the package before installing on sensitive systems.
Credentials
The skill requests no local environment variables or credentials and explicitly advises against asking users for API keys, instead using Membrane-managed connections. This is proportionate; the main concern is trusting Membrane with Timetastic credentials/data since Membrane handles auth server-side.
Persistence & Privilege
The skill is not always-on and is user-invocable. Autonomous invocation is allowed by default (platform behavior) but there are no additional persistence or system-wide config changes requested.
Assessment
This skill appears coherent for integrating Timetastic via the Membrane CLI. Before installing: (1) verify @membranehq/cli is the official package (check npm page, package repository, and checksums); (2) review Membrane's privacy/security docs because your Timetastic data and credentials will be proxied through Membrane's service; (3) avoid installing the CLI globally on sensitive production hosts — use an isolated environment or container for testing; (4) use a test Timetastic/Membrane account first to confirm behavior and permissions. If you are uncomfortable trusting an intermediary with HR data, do not proceed.Like a lobster shell, security has layers — review code before you run it.
latestvk971prymyc4ngxbd64fd877py984cbbv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.