Clockwork Recruiting
v1.0.2Clockwork Recruiting integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clockwork Recruiting data.
⭐ 0· 60·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 match the instructions: the SKILL.md explains how to use the Membrane CLI to discover connectors/actions and proxy requests to Clockwork Recruiting. Nothing in the instructions asks for unrelated credentials, binaries, or system access.
Instruction Scope
Instructions are narrowly scoped to installing/using @membranehq/cli, logging in, listing/connecting to a Clockwork connector, running actions, and proxying API calls. One notable capability: 'membrane request' allows arbitrary proxied API calls to the Clockwork API, which is expected for a connector but means the CLI (and Membrane's service) can issue arbitrary requests on your behalf once connected.
Install Mechanism
This is an instruction-only skill with no install spec. It recommends installing the Membrane CLI via npm (-g). Installing a third-party global CLI is a reasonable but non-trivial action — you should verify the package's authenticity (publisher, repository, checksum) before installing.
Credentials
No environment variables or local secrets are requested. The skill relies on a Membrane account/connection to manage credentials server-side — this is proportional to its purpose but requires trusting Membrane to handle and store your ATS credentials and to make API calls.
Persistence & Privilege
The skill does not request always:true, does not install code, and does not modify other skills or system-wide settings. Autonomous invocation (default) is allowed by platform but not excessive for this connector-style skill.
Assessment
This skill appears to do what it says: it uses Membrane to interact with Clockwork Recruiting. Before installing/use: (1) verify the @membranehq/cli npm package and GitHub repo (publisher, repo, recent releases) to avoid typosquatting; (2) review Membrane's privacy/security policies because your ATS credentials and API requests will be mediated by their service; (3) only grant the minimal Clockwork scopes you need and consider using a limited-permission account for integration; (4) be cautious installing global npm packages on shared or production machines.Like a lobster shell, security has layers — review code before you run it.
latestvk97bwyf719yxe2b7gaasn3px65843cmw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.