Documentpro
v1.0.2DocumentPro integration. Manage data, records, and automate workflows. Use when the user wants to interact with DocumentPro data.
⭐ 0· 95·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
medium confidencePurpose & Capability
The name/description (DocumentPro integration) aligns with the instructions: the skill delegates work to the Membrane CLI to discover and run actions or proxy requests against DocumentPro. Requiring a Membrane account and network access is proportionate.
Instruction Scope
The SKILL.md instructs the agent/user to install and use the Membrane CLI, perform login (browser-based or headless), discover connections/actions, run actions, and proxy arbitrary HTTP requests through Membrane. These steps are in-scope for a generic integration, but the proxy capability means Membrane will be able to send arbitrary requests on behalf of the user — so it requires trusting Membrane's service and connectors.
Install Mechanism
There is no automatic install spec in the registry; the doc recommends installing @membranehq/cli via 'npm install -g'. Using an npm package from the membranehq namespace is reasonable for this use-case, but global npm installs require caution (privilege, supply-chain and version-check considerations).
Credentials
The skill does not request environment variables or other secrets. The instructions explicitly recommend creating a Membrane connection rather than asking for API keys locally, which is proportionate to its purpose.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It does rely on a third-party service (Membrane) to hold/refresh credentials, which is an external trust decision but not a misalignment with purpose.
Assessment
This skill delegates all integration work to the Membrane service and its CLI. It does not request local secrets, but installing and using it requires: (1) installing a third-party npm package globally, (2) logging into Membrane (browser-based auth), and (3) trusting Membrane to store/refresh your DocumentPro credentials and to proxy arbitrary API requests. Before installing, verify the @membranehq/cli package and the Membrane service (npm page, GitHub repo, privacy/security docs), consider using a non-global or isolated environment (container or VM) for the CLI, and only proceed if you are comfortable with Membrane having access to your DocumentPro account data. If you need higher assurance, ask the skill author for an explicit source/repository and signed releases for the CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk975v6am8dt0atpgmawrtbn57n843cb2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.