Octoparse
v1.0.2Octoparse integration. Manage data, records, and automate workflows. Use when the user wants to interact with Octoparse data.
⭐ 0· 132·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
Name/description (Octoparse integration) matches the instructions: all runtime steps use Membrane to connect to and proxy requests to Octoparse. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent/user to install and use the Membrane CLI, create a connection, list actions, run actions, and proxy raw requests to the Octoparse API. It does not instruct reading arbitrary files, accessing unrelated environment variables, or exfiltrating data to unexpected endpoints. It does rely on Membrane to handle auth server-side.
Install Mechanism
The skill is instruction-only (no install spec), which is low risk. The README tells users to install the third-party CLI via `npm install -g @membranehq/cli` or use `npx`. Installing global npm packages has standard supply-chain/privilege considerations; verify the CLI's source and trustworthiness before installing on sensitive systems.
Credentials
The skill declares no required env vars or credentials. It explicitly tells users not to supply API keys and instead create a connection through Membrane, which is proportionate to the stated design (delegated auth).
Persistence & Privilege
Skill is not always-on and is user-invocable. There is no install-time behavior in the skill bundle itself and no instructions to modify other skills or system-wide configs beyond using the Membrane CLI for connections.
Assessment
This skill is coherent: it expects you to use the Membrane service/CLI as a proxy to Octoparse rather than managing Octoparse credentials locally. Before installing or using it, consider: (1) you will rely on a third-party service (Membrane) that will see API traffic and handle your Octoparse auth—confirm you trust their security and privacy practices; (2) the instructions ask you to install a global npm CLI—avoid installing on sensitive or production hosts without review; (3) in headless environments you will copy auth codes from a printed URL—treat those codes like secrets. If you’re uncomfortable delegating auth to Membrane, use Octoparse’s API directly or verify the Membrane project's source/reputation first.Like a lobster shell, security has layers — review code before you run it.
latestvk97dbm81gk4kpy0tpszybg0sns843pvr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.