Serpdog

v1.0.2

Serpdog integration. Manage Keywords, Websites, Competitors, Users, Projects. Use when the user wants to interact with Serpdog data.

0· 102·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Serpdog integration) matches the instructions: discover and run Serpdog-related actions via the Membrane CLI and proxy. Requiring a Membrane account and network access is expected.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Serpdog. Be aware that proxying sends requests (and whatever request payloads you provide) through Membrane's service; the skill explicitly says Membrane handles auth and credential refresh server-side.
Install Mechanism
This is an instruction-only skill (no install spec), but it instructs the user to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a normal requirement here but carries the usual supply-chain risks of installing a package from npm; verify the package source and trustworthiness if that concerns you.
Credentials
The skill declares no required environment variables or secrets and relies on Membrane-managed authentication. It does not request unrelated credentials or config paths.
Persistence & Privilege
The skill is not always-enabled and has no install-time code or configuration that would persistently alter other skills or system-wide settings. Autonomous invocation remains possible (platform default) but is not combined with other high-risk factors.
Assessment
This skill appears to do what it says: it relies on the Membrane CLI to talk to Serpdog and does not ask for unrelated credentials. Before installing: (1) confirm you trust Membrane (data and API traffic will pass through their service when using the proxy), (2) review the @membranehq/cli npm package and its publisher, (3) avoid installing global packages on critical/shared systems unless you trust the source, and (4) expect the login command to open a browser or require a headless login flow.

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

latestvk97fww9yttya7s6h9dgkp0r5vs843qem

License

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

Comments