World News Api
v1.0.0World News API integration. Manage data, records, and automate workflows. Use when the user wants to interact with World News API data.
⭐ 0· 19·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 (World News API integration) matches the instructions: use Membrane CLI to connect, discover actions, and proxy requests to the World News API. No unrelated services or secrets are requested.
Instruction Scope
The SKILL.md instructs running the Membrane CLI (including login flow and action/request commands). It does not ask the agent to read unrelated files or environment variables. Minor note: the file expects network access and an interactive or headless browser-based login, which is coherent for this workflow.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md recommends installing @membranehq/cli via npm (-g). Using npm is a common pattern; it does install third-party code system-wide when run with -g, so users should vet the package before installing. The install source is a normal public package registry (npm), not an untrusted URL or archive.
Credentials
No environment variables or credentials are requested by the skill; SKILL.md explicitly says Membrane handles credentials and advises not to ask users for API keys. This is proportionate for a connector-style skill.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide config changes. It relies on a user-installed CLI and browser-based auth; it does not attempt to persist credentials locally or modify other skills.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to World News API and intentionally avoids asking for API keys. Before installing/using: 1) verify the @membranehq/cli package on npm (publisher, download counts, source repo) since npm -g runs third-party code on your system; 2) understand that Membrane will hold and use your connection credentials (review their privacy/TOS); 3) perform the login in a browser you control and confirm what account/scopes you're granting; 4) if you want extra containment, run the CLI in an isolated environment (container or VM) rather than on your main workstation; 5) confirm whether you allow the agent to autonomously run CLI commands (the skill can be invoked by the agent when triggered). Overall, nothing in the skill requests unrelated privileges or secrets.Like a lobster shell, security has layers — review code before you run it.
latestvk971tqzc10r8swxtmc385f9bh984fx9f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
