Repsly
v1.0.0Repsly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Repsly data.
⭐ 0· 53·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description say 'Repsly integration' and the SKILL.md exclusively documents using Membrane (a proxy/connector) to access Repsly resources; required capabilities (network access, a Membrane account, and the Membrane CLI) are coherent with that purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, creating/using connections, listing actions, running actions, and proxying requests to Repsly via Membrane. The SKILL.md does not instruct reading unrelated files, system paths, or additional environment variables.
Install Mechanism
The skill is instruction-only (no install spec), but it tells users to run a global npm install of @membranehq/cli. Installing third-party CLIs globally runs remote code and requires trust in the package/publisher; this is expected for a CLI-based integration but worth caution.
Credentials
No environment variables, secrets, or config paths are declared or requested by the skill. The SKILL.md explicitly recommends letting Membrane handle credentials rather than asking users for API keys, which is consistent and minimal.
Persistence & Privilege
The skill does not request always-on presence, does not claim to modify system-wide agent settings, and is user-invocable. There is no indication it will persist credentials locally or alter other skills.
Assessment
This skill looks coherent for integrating Repsly via Membrane, but you should: (1) confirm you trust Membrane/@membranehq before installing their CLI (review the package source or use npx to avoid a global install), (2) verify the connection scopes and permissions when authenticating to Repsly, (3) prefer browser-based OAuth flows (as documented) and avoid sharing Repsly API keys with the skill, and (4) revoke the Membrane connection if you no longer need it. If you need extra assurance, inspect the Membrane CLI source code or run it in an isolated environment (container/VM) before granting access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk97cj3835cqgbmkww278y55tk584etf3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.