Contentking
v1.0.2ContentKing integration. Manage data, records, and automate workflows. Use when the user wants to interact with ContentKing data.
⭐ 0· 40·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 say 'ContentKing integration' and the instructions exclusively describe using the Membrane CLI to discover connectors, create a connection, run actions, and proxy requests to ContentKing. Required resources (network access and a Membrane account) align with this purpose.
Instruction Scope
SKILL.md only instructs installing/using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying requests. It does not instruct reading unrelated files, exporting system secrets, or sending data to endpoints other than Membrane/ContentKing. It explicitly advises not to ask users for API keys (letting Membrane handle auth).
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing @membranehq/cli via npm (global install or npx usage). Suggesting a well-scoped package from a namespaced npm package is normal, but installing global npm packages has usual trust/risk considerations — the user must trust the @membranehq package and the npm ecosystem.
Credentials
The skill declares no required env vars or credentials. Authentication is delegated to Membrane (server-side), so no local secrets are requested. This is proportional, but it means users must trust Membrane to hold and refresh the ContentKing credentials.
Persistence & Privilege
The skill does not request always: true, does not modify other skill configs, and is not requesting persistent system privileges. Autonomous invocation is allowed by default (platform normal) but not combined with other concerning privileges.
Assessment
This skill is internally consistent: it guides the agent to use the Membrane CLI to connect to ContentKing and does not ask for unrelated secrets. Before installing: (1) confirm you trust Membrane (getmembrane.com and the @membranehq npm package) because Membrane will hold/refresh your ContentKing credentials and proxy requests; (2) be aware that installing the Membrane CLI globally via npm gives that package runtime access on your machine — prefer using npx if you want to avoid a global install; (3) review Membrane's privacy and security docs and the ContentKing connector behavior if you handle sensitive site data.Like a lobster shell, security has layers — review code before you run it.
latestvk97czgj0q8v3qbmn9zfewpmt4h843tzh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.