Akamai
v1.0.0Akamai integration. Manage data, records, and automate workflows. Use when the user wants to interact with Akamai data.
⭐ 0· 59·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (Akamai integration) matches the instructions: all actions are performed via the Membrane CLI which is explicitly described. No unrelated env vars, binaries, or config paths are requested.
Instruction Scope
SKILL.md only instructs installing and using the @membranehq/cli to discover connectors, run actions, and proxy arbitrary Akamai API calls. This stays within the stated purpose, but the proxying behavior means Membrane will see all proxied requests and results — an expected but important privacy/trust implication.
Install Mechanism
There is no packaged install spec; the instructions tell the user to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package is a common pattern but is a moderate-risk operation because it pulls code from the public npm registry and writes to the system. The skill package itself does not install anything.
Credentials
The skill declares no required env vars or credentials and explicitly relies on Membrane to manage auth. This is proportionate, but it means you must trust Membrane with your Akamai credentials and requests.
Persistence & Privilege
The skill is instruction-only, does not request always:true, and does not modify other skills or system-wide configs. It has normal, limited presence (user-invocable).
Assessment
This skill appears coherent, but before installing or using it: 1) understand that all Akamai API calls and credentials are routed through Membrane — review Membrane's privacy/security practices and the @membranehq/cli project (homepage/repo) and only install the official package. 2) Installing an npm -g package modifies your system; prefer running via npx or pin a specific version if you need reproducibility. 3) Review and restrict the connector's permissions in Akamai (least privilege) and inspect any connection IDs and actions created. 4) If you need stronger assurance, audit the CLI code in the referenced GitHub repo and confirm package integrity (checksums/signatures) before installing. If you are not comfortable trusting a third party to hold and refresh your Akamai credentials, do not use this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk970avnvqe8mfddskwmj6nx0ns848ezk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.