Scout Apm

v1.0.0

Scout APM integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scout APM data.

0· 28·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description say 'Scout APM integration' and the instructions consistently show how to install Membrane CLI, create a connection to Scout APM, run actions, and proxy requests to the Scout APM API. Required tools and commands align with the stated purpose.
Instruction Scope
SKILL.md stays on-topic: it instructs installing the Membrane CLI, performing Membrane login, creating connections, listing/ running actions, and proxying Scout APM API requests through Membrane. It does not instruct reading unrelated files or environment variables. One important operational detail: network traffic and Scout APM credentials are routed through Membrane’s service (the doc explicitly says Membrane handles auth and proxies requests), so the user should be aware that data and API calls go through a third-party service.
Install Mechanism
This is an instruction-only skill (no install spec), but SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard approach but has the usual trust implications: the package comes from the public npm registry and will run locally. This is expected for the skill’s functionality but users should confirm they trust the publisher (@membranehq).
Credentials
The skill declares no required environment variables or credentials and the instructions explicitly advise not to ask users for API keys (use Membrane connections instead). Requiring a Membrane account and CLI login is proportional to the goal of using Membrane as an auth/proxy layer for Scout APM.
Persistence & Privilege
The skill does not request always: true, and there is no indication it modifies other skills or system-wide settings. Membrane login will create local auth state (normal for a CLI) but the SKILL.md does not instruct elevated or persistent system-wide changes beyond that.
Assessment
This skill is coherent but relies on the Membrane service and its CLI: installing `@membranehq/cli` and logging into a Membrane account will route Scout APM API calls through Membrane and store connection tokens via Membrane. Before installing, confirm you trust Membrane (review their docs, privacy, and npm package publisher), and that you’re comfortable routing your Scout APM data and credentials through that third-party. If you prefer not to use a proxy service, you should integrate directly with Scout APM’s API using your own credentials. In CI or headless environments follow the documented headless login pattern carefully, and revoke connections or tokens in your Membrane account if you need to remove access later.

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

latestvk97b61ap8k2zprjndycprkc8wn846wpx

License

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

Comments