Tick
v1.0.0Tick integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tick data.
⭐ 0· 52·0 current·0 all-time
byMembrane Dev@membranedev
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 (Tick integration) matches the instructions: install the Membrane CLI, create a Membrane connection to Tick, list/run actions, and proxy requests. Requiring Membrane (a third‑party integration broker) is consistent with the stated purpose.
Instruction Scope
SKILL.md stays on-topic: it instructs installing the Membrane CLI, logging in, creating connections, listing and running actions, and proxying requests through Membrane. It does not ask the agent to read unrelated files, environment variables, or system configuration. Note: using Membrane means Tick API calls (and possibly data) will flow through Membrane's service — this is expected for this integration but important for user privacy/security awareness.
Install Mechanism
There is no registry install spec for the skill itself (instruction-only), but the doc recommends installing @membranehq/cli via npm (-g). Installing a third-party CLI globally is a reasonable developer step here but carries the usual risks of any npm package; users should review the package and source before installing.
Credentials
The skill declares no required environment variables or local credentials and explicitly advises letting Membrane handle auth and not asking users for API keys. The auth flow is via Membrane's login/connection process, which is proportionate to the integration.
Persistence & Privilege
The skill is not marked always:true and is user-invocable. It does not request persistent system changes or access to other skills' configurations. Autonomous invocation is allowed by platform default (not flagged by itself).
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to connect to Tick rather than handling Tick credentials itself. Before installing or using it, consider: (1) Membrane will broker API calls and therefore will see/act on your Tick data—review Membrane's privacy/security policies and the connector permissions. (2) The instructions recommend installing an npm CLI globally—review @membranehq/cli source and npm package trustworthiness first. (3) The OAuth/login flow opens a browser and issues tokens via Membrane; ensure you only complete auth for accounts you intend to connect. If you need tighter control, prefer creating limited-scope Tick accounts or audit what actions/connections you create in Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97an1m9z49f4s8whnhrrg7sdh84dnky
License
MIT-0
Free to use, modify, and redistribute. No attribution required.