Paycaptain
v1.0.2PayCaptain integration. Manage data, records, and automate workflows. Use when the user wants to interact with PayCaptain data.
⭐ 0· 75·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
medium confidencePurpose & Capability
The SKILL.md describes connecting to PayCaptain and performing actions via the Membrane CLI. All required capabilities (interactive login, connection creation, action listing/running, proxying requests) are consistent with a PayCaptain integration.
Instruction Scope
Runtime instructions are limited to installing/using the official @membranehq/cli, authenticating via membrane login, creating a connection, listing and running actions, and proxying requests. These are narrowly scoped to the integration. Note: using this skill will route requests and PayCaptain data through Membrane's service (server-side auth and proxying), so sensitive payroll data will transit external infrastructure.
Install Mechanism
There is no automated install spec in the package; the SKILL.md asks users to install the Membrane CLI via npm (npm install -g @membranehq/cli) or use npx. This uses the public npm registry (moderate risk) rather than arbitrary downloads. Installing global npm packages requires attention to package provenance and privileges.
Credentials
The skill requests no environment variables or local credentials and relies on Membrane to manage auth. This is proportionate to the stated purpose. Reminder: trust in Membrane's handling of credentials and data is required because Membrane acts as a proxy and stores/refreshes tokens server-side.
Persistence & Privilege
always:false and no install-time modifications are requested. The skill is instruction-only and does not claim persistent elevated privileges or alter other skills or system-wide config.
Assessment
This skill is coherent: it simply instructs you to use the Membrane CLI to connect to PayCaptain and run API actions. Before installing or using it, verify the @membranehq/cli package on npm (and prefer using npx to avoid a global install if you want lower system impact), confirm you trust Membrane as a third-party proxy (it will broker and potentially store sensitive payroll/employee data and auth tokens), and be aware the login flow opens a browser for authentication. Because the skill source is listed as unknown in the registry metadata, consider checking Membrane's official docs and the @membranehq package repository for authenticity and review their privacy/security policies. If you operate in a regulated environment, get sign-off from your security/privacy team before routing payroll data through a third-party service.Like a lobster shell, security has layers — review code before you run it.
latestvk97dkx5fdp7t37ccvj1cjpt4y1842waj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.