Cisco Appdynamics
v1.0.2Cisco AppDynamics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco AppDynamics data.
⭐ 0· 79·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
medium confidencePurpose & Capability
Name/description say 'Cisco AppDynamics' and the instructions exclusively use the Membrane CLI to discover, connect to, and proxy requests to AppDynamics — this is coherent with the stated purpose.
Instruction Scope
SKILL.md confines runtime actions to using the Membrane CLI (login, connection, action list/run, request proxy). It does not instruct the agent to read unrelated files, environment variables, or exfiltrate data to unknown endpoints. It does rely on Membrane to handle auth and proxy requests to AppDynamics.
Install Mechanism
There is no automatic install spec in the skill bundle; the doc tells the user to run `npm install -g @membranehq/cli`. This is expected for a CLI-driven integration but carries the usual risk of installing a third‑party global npm package — verify the package/publisher and prefer non-global installs if appropriate.
Credentials
The skill declares no required env vars, no primary credential, and no config paths. It relies on a Membrane account for authentication rather than asking for AppDynamics API keys locally, which is proportional given the design.
Persistence & Privilege
Skill flags show always:false and normal autonomous invocation. The skill does not request persistent system-wide privileges or attempt to modify other skills/configs.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Cisco AppDynamics. Before installing or using it: 1) Verify the @membranehq/cli package and its publisher (check the GitHub repo, package maintainer, and recent release history) before running a global npm install — global npm installs can run arbitrary install scripts. 2) Understand that Membrane will broker requests and store/refresh credentials server-side — ensure you trust Membrane (getmembrane.com) and its security/privacy policies because your AppDynamics data and auth flows will pass through their service. 3) If you prefer less system impact, consider using a scoped/local install (npx or project-level install) rather than a global install. 4) If you need stronger assurance, ask the skill author for source verification or for a version pinned to a known-good release.Like a lobster shell, security has layers — review code before you run it.
latestvk976n8ewsnj4rqceswsjqg3wz9842avm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.