Docparser
v1.0.2Docparser integration. Manage Organizations. Use when the user wants to interact with Docparser data.
⭐ 0· 127·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
The name/description (Docparser integration) match the instructions: everything is performed via the Membrane CLI which proxies to Docparser. Small metadata inconsistency: registry metadata lists no required binaries, but the SKILL.md expects the 'membrane' CLI to be installed and used at runtime.
Instruction Scope
SKILL.md stays on-topic: it describes installing the Membrane CLI, logging in, creating/using a Docparser connection, running pre-built actions, and using a proxy request feature. It does not instruct reading unrelated files or environment variables. It does, however, rely on sending data (documents/requests) through Membrane's service.
Install Mechanism
There is no formal install spec in the registry entry, but the README instructs a global npm install: 'npm install -g @membranehq/cli'. That is an npm registry package (traceable) but global npm installs run third‑party code on your machine and can alter PATH; this is a moderate-risk install step that should be vetted (package provenance, checksum/version pinning).
Credentials
The skill requests no local environment variables or credentials. Instead it expects you to authenticate via Membrane (browser-based login). This is proportional to the stated purpose, but it means Docparser requests and document content will be proxied through Membrane — a privacy/third‑party exposure consideration.
Persistence & Privilege
The skill does not request always:true, does not claim to run autonomously beyond normal platform behavior, and does not ask to modify other skills or system-wide configs. Normal autonomy settings apply.
Assessment
This skill is coherent: it uses the Membrane CLI to access Docparser rather than talking to Docparser directly. Before installing/use: (1) verify and trust the @membranehq/cli npm package (check package page, publisher, pinned version, and integrity), (2) review Membrane's privacy/security policy because document contents and Docparser credentials will be proxied/managed by their service, (3) prefer using a dedicated/non-sensitive account or test data first, and (4) avoid global installs on sensitive machines (consider using a container, VM, or npx for ad-hoc use). If you cannot or do not want to route documents through a third party, prefer a direct Docparser integration that you control.Like a lobster shell, security has layers — review code before you run it.
latestvk9760yqy6htdxt5xtsj0hy4m5s842y4e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.