Hyperping

v1.0.0

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

0· 61·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 skill describes a Hyperping integration that operates via the Membrane platform and instructs use of the @membranehq/cli. That is consistent with the stated purpose. Minor inconsistency: metadata lists no required binaries, but the instructions require installing/using npm and the Membrane CLI (so the environment must have npm/node or an existing membrane binary).
Instruction Scope
SKILL.md stays on topic: it only tells the agent to install and use the Membrane CLI to discover connectors, create connections, list and run actions, and proxy requests to Hyperping. It does not instruct reading arbitrary local files or exfiltrating unrelated data. Note: the 'membrane request' proxy allows sending arbitrary paths to the Hyperping API through the Membrane service — expected for this integration but worth understanding.
Install Mechanism
There is no automated install spec in the skill bundle (lowest risk). The doc recommends a user-run npm global install of @membranehq/cli, which is a standard public-package install pattern. Installing a global npm package is a normal step but requires trusting that package and npm as the distribution channel.
Credentials
The skill declares no environment variables and uses Membrane's browser-based login flow rather than asking for API keys locally — proportional for the described functionality. The tradeoff: Membrane (a third party) will hold and refresh Hyperping credentials on your behalf, so you must trust that service with access to your Hyperping account.
Persistence & Privilege
The skill does not request always:true, does not declare any system config paths, and is user-invocable only. It does not ask to modify other skills or system settings.
Assessment
This skill is coherent: it uses Membrane as an intermediary to manage Hyperping access and asks you to install the Membrane CLI. Before proceeding, ensure you are comfortable with the following: 1) installing a global npm package (@membranehq/cli) — verify the package name and source on npm and the vendor's homepage; 2) trusting Membrane to store and refresh your Hyperping credentials (you delegate API access to a third party); 3) having npm/node available in the environment (the metadata did not list this requirement); and 4) the membrane request proxy can call arbitrary Hyperping endpoints for any established connection, so limit connector scope if possible. If you need stronger assurance, ask the publisher for the CLI package link and repository, review the npm package, or run the integration in a controlled environment before granting it access to production accounts.

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

latestvk97b6thnfx0nqs35zafvky74f184bpaz

License

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

Comments