Bytenite

v1.0.0

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

0· 60·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 README-style SKILL.md describes using the Membrane CLI to manage ByteNite data; requiring the Membrane CLI and a Membrane account is coherent with the stated ByteNite-integration purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, logging in, creating connections, listing/running actions, and optionally proxying requests through Membrane. There are no steps telling the agent to read local files, hunt for unrelated credentials, or send data to arbitrary endpoints outside Membrane/ByteNite.
Install Mechanism
There is no formal install spec, but SKILL.md instructs users to run 'npm install -g @membranehq/cli' (or use npx). Global npm installs execute third-party code on the host and carry the usual risks; this is proportionate to the skill's need but users should verify the package source and consider using npx/pinned versions or inspecting the package before global installation.
Credentials
The skill declares no required env vars or credentials and explicitly instructs to let Membrane handle auth rather than asking users for API keys. That is proportionate for a connector-based integration.
Persistence & Privilege
The skill is instruction-only, does not request permanent presence, does not modify other skills or system-wide settings, and 'always' is false. Autonomous invocation is allowed (platform default) and is not on its own a concern here.
Assessment
This skill is instruction-only and internally consistent, but it relies on a third-party service (Membrane) and an npm package. Before installing/use: 1) Verify the Membrane service (https://getmembrane.com) and the @membranehq/cli npm package (check publisher, version, and release notes). 2) Prefer using npx or pin a specific CLI version instead of an unrestricted global npm install; inspect package contents if possible. 3) Understand that Membrane will proxy requests and therefore will see request/response data and hold delegated credentials — review their privacy/security docs and restrict what account you connect (use least-privilege/test accounts where possible). 4) Confirm the official ByteNite API docs and the repo referenced (https://github.com/membranedev/application-skills) to ensure authenticity. 5) If you need higher assurance, request an explicit install spec or signed package metadata from the publisher.

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

latestvk97dmtsq4yn5wjk4mg25r6naz5845559

License

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

Comments