Ceridian Dayforce
v1.0.0Ceridian Dayforce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ceridian Dayforce data.
⭐ 0· 51·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/description match the runtime instructions: the SKILL.md describes using the Membrane CLI to interact with Ceridian Dayforce (discover connectors, create connections, run actions, or proxy API requests). Requiring the Membrane CLI and a Membrane account is coherent with that stated purpose.
Instruction Scope
Instructions stay within the integration purpose (install membrane CLI, log in, connect, list and run actions, proxy requests). One noteworthy item: the Membrane proxy feature lets you send arbitrary requests to Dayforce endpoints (and potentially arbitrary paths) — this is expected for a proxy but means the agent/operator must avoid sending sensitive data inadvertently. The SKILL.md does not instruct reading unrelated files or environment variables.
Install Mechanism
No bundled install spec; SKILL.md asks the operator to install @membranehq/cli via npm -g. Installing an official npm CLI for a third-party integration is proportionate. (The doc even uses npx in examples, which avoids a global install.)
Credentials
The skill declares no required environment variables or credentials and explicitly tells users to let Membrane manage credentials server-side. That aligns with the described behavior and avoids local secret requests.
Persistence & Privilege
Skill is user-invocable, not always-enabled, and does not request persistence or system-wide changes. There is no indication it modifies other skills or agent configs.
Assessment
This skill appears coherent and limited to using the Membrane CLI to access Ceridian Dayforce. Before installing, consider: (1) Trust: you are delegating auth and API access to Membrane—verify you trust that provider and your organization’s policy allows it. (2) Package provenance: install @membranehq/cli from the official npm registry (or use npx) and confirm the package/author page if you need higher assurance. (3) Data safety: be careful when using the proxy or running arbitrary actions—don't send PII/credentials to endpoints unless you intend to. (4) Environment: prefer ephemeral or per-user installs (npx) if you cannot audit global npm installs. If you need stronger assurance, ask the publisher for a signed release or an explicit privacy/security statement from Membrane about how Dayforce credentials and data are handled.Like a lobster shell, security has layers — review code before you run it.
latestvk97bna95t6jdqfhcfwv6svyty984c706
License
MIT-0
Free to use, modify, and redistribute. No attribution required.