Typingdna
v1.0.2TypingDNA integration. Manage data, records, and automate workflows. Use when the user wants to interact with TypingDNA data.
⭐ 0· 54·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
The name/description say TypingDNA integration and the SKILL.md only documents using the Membrane CLI to connect to and proxy requests to TypingDNA. There are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI (login, connect, action list/run, request proxy). The instructions do not ask the agent to read local files or unrelated credentials. Note: proxying requests means request payloads and TypingDNA API traffic will flow through Membrane's servers (expected for this design).
Install Mechanism
The document recommends installing @membranehq/cli via npm -g or using npx. This is a standard but moderate-risk install vector because npm packages execute code locally; the skill itself has no built-in install spec and no direct downloads from untrusted URLs.
Credentials
No environment variables or credentials are requested by the skill. It explicitly delegates credential management to Membrane and requires only a Membrane account and network access, which is proportional for a proxy-based integration.
Persistence & Privilege
Skill is instruction-only, not always:true, user-invocable, and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill is coherent but you should: 1) Review the @membranehq/cli npm package (publisher, recent releases, and reviews) before installing global packages. 2) Be aware Membrane will proxy TypingDNA API calls — any biometric or sensitive payloads will transit and may be stored/processed by Membrane; confirm this meets your privacy/compliance requirements. 3) Prefer using npx to avoid a global install if you want less surface area. 4) Verify the Membrane account/browser-auth flow is appropriate for your environment (headless use requires copying codes). 5) If you handle sensitive user biometrics, validate consent and retention policies with both TypingDNA and Membrane before sending real data.Like a lobster shell, security has layers — review code before you run it.
latestvk97er2cgc5t21m5v0rnj9zt6nn843he9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.