Dayschedule
v1.0.2DaySchedule integration. Manage Users, Roles, Organizations, Projects, Activities, Notes and more. Use when the user wants to interact with DaySchedule data.
⭐ 0· 87·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 and description say this is a DaySchedule integration; the SKILL.md exclusively instructs use of the Membrane CLI and Membrane connections to access DaySchedule APIs. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to DaySchedule. They do not instruct reading arbitrary files or environment variables, nor do they direct data to unexpected endpoints beyond Membrane/DaySchedule.
Install Mechanism
The SKILL.md recommends a global npm install (npm install -g @membranehq/cli). This is a common and reasonable instruction for this integration, but installing global npm packages writes software to disk and should be done only from trusted sources. The instruction-only skill itself does not perform any installs automatically.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The README explicitly instructs to let Membrane handle credentials and not to ask users for API keys, which is proportionate for a proxy-based integration.
Persistence & Privilege
always is false and there are no install scripts or other mechanisms that would give the skill persistent elevated presence. The skill is instruction-only and does not modify other skills or global agent settings.
Assessment
This skill appears coherent: it relies on the Membrane CLI to authenticate and proxy requests to DaySchedule rather than asking for raw API keys. Before installing the CLI, verify the npm package identity (@membranehq/cli) and repository (inspect the package on npm/GitHub) and install it from a trusted environment. When completing the Membrane login in a browser, review the scope/permissions requested — that determines what DaySchedule data Membrane can access. If you prefer not to install new global packages on your machine, you can run the CLI in a container or sandbox. Because this is instruction-only, the skill itself does not exfiltrate secrets or require extra credentials, but granting Membrane access to DaySchedule will allow it to act on your behalf, so only proceed if you trust the Membrane service.Like a lobster shell, security has layers — review code before you run it.
latestvk972brz61aa81ed228bcztef298438fn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.