Timewax

v1.0.2

Timewax integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timewax data.

0· 93·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes a Timewax integration and consistently instructs the agent to use the Membrane CLI to connect to Timewax. Requiring the Membrane CLI and a Membrane account is appropriate for a third-party integration proxy; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
The runtime instructions are limited to installing the Membrane CLI, logging in (browser-based or headless flow), locating the Timewax connector, and creating connections. The instructions do not direct the agent to read arbitrary local files, export unrelated environment variables, or send data to unexpected endpoints beyond Membrane/Timewax.
Install Mechanism
Installation is an npm global package install (npm install -g @membranehq/cli). Using the npm registry is expected for a CLI package, but global npm installs can require elevated privileges and npm packages may run install scripts—this is normal but worth noting from a system-administration perspective. No downloads from untrusted URLs or archive extraction are used.
Credentials
The skill declares no required environment variables or secrets. Authentication is handled interactively by the Membrane CLI. That design keeps credential handling proportional to the skill's purpose, though it does mean you must trust Membrane to manage your Timewax credentials.
Persistence & Privilege
The skill is instruction-only, does not request always: true, and does not claim to modify other skills or global agent settings. Autonomous invocation is allowed by default (normal); there are no additional persistence or privilege requests in the manifest.
Assessment
This skill is coherent: it relies on the Membrane CLI to access Timewax and requires a Membrane account and network access. Before installing, verify the @membranehq/cli package on the npm registry and the Membrane project (homepage/repo) if you want to confirm provenance. Note that npm -g may require admin rights; if you prefer less system impact you can run the CLI via npx or install it in a controlled environment. Also be aware that Membrane will manage your Timewax credentials — only proceed if you trust that service to access and store those credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97efsmf48c1yxtp8wxb5cn7098432cg

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments