Dingconnect

v1.0.2

DingConnect integration. Manage data, records, and automate workflows. Use when the user wants to interact with DingConnect data.

0· 78·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the instructions: the skill uses Membrane to operate on DingConnect data. One minor inconsistency: registry metadata lists no required binaries, but the runtime instructions explicitly require installing/running the Membrane CLI (npm/npx). This is expected for a CLI-based integration but the metadata omission should be noted.
Instruction Scope
SKILL.md stays on-topic: it instructs installing and using the Membrane CLI, creating a connection, running pre-built actions, or proxying API requests via Membrane. It does not instruct reading unrelated local files or asking for unrelated environment variables. It does rely on browser-based login and network access, which are declared in the header.
Install Mechanism
There is no formal install spec in the registry, but the instructions tell users to install @membranehq/cli via npm -g or use npx. Installing a global npm package is common but carries the normal risks of running third-party npm code; there are no direct downloads or archive extractions in the instructions.
Credentials
The skill does not request environment variables or credentials in SKILL.md and explicitly advises not to ask users for API keys. Authentication is delegated to Membrane (server-side). The main proportionate concern is trusting Membrane with the DingConnect credentials and proxied data.
Persistence & Privilege
Skill is user-invocable and not forced-always; it does not request persistent agent privileges or modify other skills. The agent can invoke it autonomously (platform default) but the skill itself does not demand elevated persistence.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to interact with DingConnect and does not ask for local API keys. Before installing: verify the @membranehq/cli package and the vendor (getmembrane.com / GitHub repository) are trustworthy, because installing a global npm CLI runs third-party code on your system. If you have concerns, prefer running commands with npx or in an isolated environment (container/VM) rather than installing globally. Understand that connecting will allow Membrane to store and use your DingConnect credentials (server-side) and proxy requests — confirm this meets your privacy/compliance requirements. Finally, note the registry metadata omits the requirement to have npm/node or the CLI — the SKILL.md is the authoritative runtime instruction.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ap7qwtnstfkcznvthrgxwm9843y88

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments