Docraptor
v1.0.0DocRaptor integration. Manage data, records, and automate workflows. Use when the user wants to interact with DocRaptor data.
⭐ 0· 182·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 (DocRaptor integration) matches the runtime instructions: all examples call the Membrane CLI to discover connectors, create a DocRaptor connection, run actions, and proxy requests. There are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, logging in via browser, creating a connection to DocRaptor, running pre-built actions, and proxying requests. Note: proxy feature allows arbitrary requests to the DocRaptor API via Membrane — expected for this integration but means Membrane will handle and relay the API calls and auth.
Install Mechanism
No install spec in the skill bundle itself; the SKILL.md recommends installing @membranehq/cli via npm install -g. Using a global npm package is a common, reasonable step for a CLI but carries the usual tradeoffs (code from the npm package will run on the user's system). This is proportionate to the stated purpose.
Credentials
The skill declares no required environment variables or credentials. The instructions explicitly say to let Membrane handle credentials and not to ask users for API keys — that is coherent and minimal.
Persistence & Privilege
Skill is instruction-only, has no install hooks, and is not marked always:true. It does not request persistent system-wide privileges or to modify other skills' configs. The agent-autonomy flags are default and acceptable.
Assessment
This skill is coherent: it uses the Membrane CLI to access DocRaptor and does not ask for extra credentials. Before installing, consider: (1) you will install a global npm package (@membranehq/cli) — review that package and its publisher; (2) authentication is handled via Membrane (browser login and server-side credential storage), so evaluate whether you trust Membrane to store and proxy access to your DocRaptor account; (3) the proxy command can send arbitrary API requests to DocRaptor through Membrane — make sure that behavior aligns with your privacy/compliance needs. If you prefer not to grant a third party proxy access to your documents, use direct DocRaptor API calls with your own managed credentials instead.Like a lobster shell, security has layers — review code before you run it.
latestvk972grqawhrv05x8j4xkf8m6kn82tscz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.