Accredible

v1.0.2

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

0· 109·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
Name/description claim Accredible integration and the instructions consistently use Membrane to connect to Accredible. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md stays on-topic: it instructs installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. It does not ask the agent to read arbitrary files, system secrets, or send data to unexpected endpoints.
Install Mechanism
There is no registry install spec, but the instructions require running `npm install -g @membranehq/cli` which pulls code from the public npm registry. This is expected for a CLI-based integration but is a moderate-risk action (global npm installs execute third-party code). The SKILL.md does not pin a version.
Credentials
The skill declares no required environment variables or credentials and explicitly delegates auth to Membrane. This is proportionate to its purpose, though it implies trusting Membrane to manage Accredible credentials server-side.
Persistence & Privilege
The skill is instruction-only, has no always:true flag, and doesn't request persistent modifications to other skills or agent-wide settings. Agent autonomous invocation remains the default platform behavior.
Assessment
This skill appears coherent: it uses the Membrane CLI to connect to Accredible and does not ask for unrelated secrets. Before installing or running it, verify the @membranehq/cli package and publisher on npm (consider pinning a version), and confirm you trust Membrane to hold Accredible credentials because Membrane will act as a proxy and manage auth. Install the CLI in an isolated or non-admin environment (container or VM) if you want to limit exposure from a global npm install. Use least-privileged/test Accredible accounts when first granting access, review Membrane's privacy/security docs, and do not paste Accredible API keys into the agent (the skill advises against that).

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

latestvk978kxepxrmvtrz29b9j77wrj9843vwb

License

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

Comments