Paylocity
v1.0.0Paylocity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Paylocity data.
⭐ 0· 28·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the runtime instructions: all actions are performed via the Membrane CLI and/or Membrane proxy to talk to Paylocity. No unrelated services or credentials are requested.
Instruction Scope
SKILL.md only instructs the agent/operator to install and use the Membrane CLI, create/list connections, run actions, and proxy requests to Paylocity. It does not ask the agent to read unrelated files, environment variables, or exfiltrate data to unexpected endpoints. It explicitly advises against asking users for API keys.
Install Mechanism
The skill package contains no install spec (instruction-only), which is low-risk. The doc instructs users to install @membranehq/cli via npm (-g). This is a normal, traceable install path but requires the user to trust the npm package and the Membrane service.
Credentials
No required environment variables or config paths are declared. The SKILL.md states that Membrane handles auth server-side and explicitly tells integrators not to collect API keys locally—this is proportionate for a connector skill.
Persistence & Privilege
The skill is not always-enabled and has no install-time persistence. It does not request modification of other skills or system-wide settings. Autonomous invocation is allowed by default but is not combined with broad credentials or elevated privileges here.
Assessment
This skill is an instruction-only integration that uses the Membrane CLI to connect to Paylocity; it does not itself request secrets or write code on your machine. Before installing or following the instructions: (1) verify the @membranehq/cli npm package page and publisher to ensure you trust the binary you will install globally; (2) confirm your organization’s policy for sending HR/payroll data through a third-party proxy (Membrane) and read their privacy/security docs and SLA; (3) follow the skill guidance to avoid pasting API keys into chat—use the official connection flow; and (4) if you need stronger assurance, inspect the Membrane CLI source or run it in an isolated environment before granting production access.Like a lobster shell, security has layers — review code before you run it.
latestvk97eqwwdnkkwvwpfpa57fjnz2s848pqk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.