Adobe Pdf Services

v1.0.2

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

0· 88·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
medium confidence
Purpose & Capability
The name, description, and runtime instructions all describe integrating with Adobe PDF Services via the Membrane CLI. Asking users to install @membranehq/cli and create a Membrane connection is proportionate to this purpose.
Instruction Scope
Instructions stay within PDF service integration (login, create connection, list/run actions, and proxy Adobe API calls). However, runtime actions (membrane request / membrane action run) will route requests and potentially document contents through Membrane's infrastructure, so users should be aware data is sent to that third party.
Install Mechanism
The skill is instruction-only but instructs the user to install a global npm package (npm install -g @membranehq/cli). This is a public npm install (moderate risk)—normal for a CLI but it writes a binary to the system and you should verify the package source and trustworthiness before installing globally.
Credentials
No environment variables, keys, or config paths are requested by the skill. Authentication is delegated to Membrane's browser flow, which is proportionate to the described workflow.
Persistence & Privilege
The skill does not request always:true, nor does it modify other skills or system-wide settings. It relies on an external CLI and account but does not demand elevated platform privileges.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to talk to Adobe PDF Services. Before installing or using it, verify you trust Membrane (getmembrane.com/@membranehq package and their privacy/security policies) because document data and API requests will be routed through their service. If you handle sensitive documents, avoid sending them until you confirm how Membrane stores/transmits data; consider using a dedicated account with limited access, installing the CLI in an isolated environment (container/VM), and checking the @membranehq/cli package source on npm/GitHub before running a global npm install.

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

latestvk973fveaatm4xqre433hj3ryqh84328c

License

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

Comments