New Relic

v1.0.2

New Relic integration. Manage Accounts. Use when the user wants to interact with New Relic data.

0· 113·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 promise New Relic integration and the SKILL.md exclusively documents using the Membrane CLI to connect to New Relic, list actions, run actions, and proxy API requests — all coherent with that purpose.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, performing user-driven login/connection flows, listing and running New Relic actions, and calling the New Relic API via Membrane's proxy. The instructions do not ask the agent to read unrelated system files, other credentials, or exfiltrate data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry, but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a public npm CLI is a reasonable step for this integration, but global npm installs should be performed only after verifying the package and publisher.
Credentials
The skill declares no required environment variables or credentials. It relies on an interactive Membrane account login and browser-based OAuth to New Relic (handled by Membrane), which is proportionate for this integration.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not require system-wide configuration changes. Agent autonomous invocation is allowed by default but is not combined with other red flags here.
Assessment
This skill is instruction-only and appears to be what it says: a New Relic integration that uses the Membrane CLI. Before proceeding: (1) verify you trust Membrane/@membranehq (check the npm package, GitHub repo, and homepage), (2) be cautious when running global npm installs and running CLI commands that open browser-based auth flows, and (3) understand that using the skill will grant the Membrane-managed connection the ability to call New Relic APIs on your behalf (authenticate via the browser to control scope). The skill itself does not request unrelated credentials or file access.

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

latestvk9772dnqx0z7p4ys85c5p4w1bx842jw9

License

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

Comments