Dailybot
v1.0.2DailyBot integration. Manage Users, Roles, Goals, Organizations. Use when the user wants to interact with DailyBot data.
⭐ 0· 141·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 uses Membrane as a connector/proxy to interact with DailyBot, which legitimately requires a Membrane account and connector setup.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. Note: the 'membrane request' proxy can be used to send arbitrary API calls through the user's Membrane connection, which is expected for a connector skill but is a capability you should be aware of.
Install Mechanism
There is no install spec in the skill bundle (instruction-only). The README tells users to run 'npm install -g @membranehq/cli' manually; that external installation is not performed by the skill itself but is a user action—verify the CLI package and source before installing globally.
Credentials
The skill declares no required environment variables, secrets, or config paths. It correctly delegates credential handling to Membrane rather than requesting API keys itself.
Persistence & Privilege
Skill is not always-enabled and does not request elevated persistence or modify other skills. It allows normal autonomous invocation (default), which is expected for skills.
Assessment
This skill is coherent but you should: 1) Verify you trust the Membrane CLI (@membranehq/cli) before installing it globally (check the npm package and upstream repo). 2) Understand that connecting your DailyBot account via Membrane grants the CLI (and any actions run through it) the ability to read and act on your DailyBot data — only create connections you intend to authorize and review requested scopes in the browser auth step. 3) Be careful when allowing the agent to run 'membrane request' or arbitrary actions: those let the agent send custom API calls through your connection. 4) If you need stricter controls, run Membrane commands manually rather than giving the agent autonomous execution, and verify the connector ID and outputs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk9732m09xt72a4yc6xb7p965v9842kna
License
MIT-0
Free to use, modify, and redistribute. No attribution required.