Donedone
v1.0.2DoneDone integration. Manage Projects, Companies. Use when the user wants to interact with DoneDone data.
⭐ 0· 215·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 and description say DoneDone integration; the SKILL.md exclusively documents using the Membrane CLI and Membrane connections/proxy to talk to DoneDone. Requesting a Membrane account and CLI is coherent with that purpose.
Instruction Scope
Runtime instructions only cover installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the DoneDone API. There are no instructions to read unrelated files, environment variables, or system configuration. The skill describes actions that may modify or delete DoneDone resources (e.g., delete-task) which is expected for an integration but worth user caution.
Install Mechanism
The skill is instruction-only (no install spec). SKILL.md recommends installing @membranehq/cli globally via npm (npm install -g). This is typical for CLI-based integrations but requires the user to trust and install a third-party npm package on their system.
Credentials
The skill declares no required env vars or credentials. However, it relies on the Membrane service to store and manage DoneDone credentials and to proxy API calls — installing and using this skill means trusting Membrane with access to your DoneDone data and credentials. That trust is proportional but should be explicit to the user.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It is an on-demand, user-invocable integration; normal autonomous invocation is allowed but not unusual for skills. No instructions attempt to modify other skills or system-wide settings.
Assessment
This skill is coherent: it simply documents how to use the Membrane CLI to connect to DoneDone. Before installing or using it, consider: (1) You must install the third-party npm package @membranehq/cli — verify the package and its GitHub repo and only install in environments you control. (2) Membrane will act as a proxy and will hold credentials/see API requests and responses — review Membrane's privacy/terms and ensure you trust them with your DoneDone data. (3) Actions include destructive operations (delete-task, delete-conversation); test with read-only queries or a test account first and avoid running destructive commands without explicit user confirmation. (4) In headless or shared environments, avoid installing global npm packages or run the CLI in an isolated/containerized environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97dhrf36j2cwvsps0k0x8k035842nvs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.