Documint
v1.0.2Documint integration. Manage Documents, Templates, Folders, Users, Teams, Workspaces. Use when the user wants to interact with Documint data.
⭐ 0· 66·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
Skill name/description say 'Documint integration' and the SKILL.md only instructs using the Membrane CLI to connect to Documint, list actions, run actions, or proxy API requests — this matches the stated purpose.
Instruction Scope
Instructions remain within scope (install Membrane CLI, login, create/list connections, run actions, proxy requests). They do instruct the agent/operator to send API requests and document data through Membrane's proxy — this will transmit user document content and request payloads to Membrane and Documint, which is expected for the integration but is a data-exposure consideration.
Install Mechanism
No install spec is embedded in the registry metadata, but SKILL.md asks the user to run 'npm install -g @membranehq/cli'. That's a public npm package install (moderate-risk operation) rather than a direct download; it's reasonable for the stated workflow but the skill should have declared the dependency in metadata for clarity.
Credentials
The skill declares no required environment variables or credentials and explicitly advises letting Membrane handle auth. That aligns with the instructions. Note: authentication occurs via Membrane (browser login) and Membrane will hold tokens/credentials server-side — so secrets are not requested locally, but access to user Documint data will be granted to Membrane.
Persistence & Privilege
always is false and there is no install-time persistence or modifications of other skills or system-wide settings. The skill is instruction-only and does not request elevated platform privileges.
Assessment
This integration appears to be what it claims: it uses the Membrane CLI to talk to Documint. Before installing/use: (1) Review and verify the @membranehq/cli npm package (source, maintainer, version) before running a global install; consider installing locally or in a container if you cannot trust global packages. (2) Understand that documents and request payloads will be proxied through Membrane — review Membrane's privacy/security policy and trustworthiness before sending sensitive PII/PHI or secrets. (3) Use a least-privilege Membrane/Documint account or dedicated workspace for testing, and verify what scopes the Documint connector requests during the OAuth flow. (4) If you need an offline or self-hosted integration, confirm whether Membrane supports that model; otherwise avoid sending highly sensitive data through a third-party service.Like a lobster shell, security has layers — review code before you run it.
latestvk979hn28175re2yqketf42b03h842c7k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.