Accountscore
v1.0.0AccountScore integration. Manage data, records, and automate workflows. Use when the user wants to interact with AccountScore data.
⭐ 0· 58·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (AccountScore integration) match the instructions: the skill exclusively documents using Membrane to connect to AccountScore, list actions, run actions, and proxy requests. Nothing in the skill requests unrelated services or credentials.
Instruction Scope
SKILL.md only instructs installing/using the Membrane CLI, logging in, creating connections, listing/running actions, and proxied requests. It does not instruct reading local files, environment variables, or sending data to unexpected endpoints beyond Membrane/AccountScore.
Install Mechanism
The registry contains no install spec (instruction-only). The doc recommends installing @membranehq/cli globally via npm (npm install -g). That is expected for a CLI-based integration, but global npm installs can affect the host environment — consider using npx or otherwise vetting the package before installing.
Credentials
The skill declares no required env vars or credentials. The instructions explicitly rely on Membrane to handle authentication and advise against collecting API keys locally, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It is instruction-only and does not request persistent system modifications or cross-skill configuration changes.
Assessment
This skill is instruction-only and coherent, but review these practical points before installing/using it:
- The integration routes requests through Membrane: Membrane will see and handle AccountScore credentials and proxied API traffic, so verify you trust Membrane (review privacy, security, and OAuth scopes) before granting access.
- The SKILL.md suggests installing @membranehq/cli globally via npm; consider using npx @membranehq/cli@latest or installing in a virtual environment to avoid altering your system PATH and to ensure you're installing the official package.
- During 'membrane login' you'll perform browser-based auth — check the OAuth consent screen and requested scopes before approving.
- If you operate in a sensitive environment, test in an isolated account or sandbox first to confirm which AccountScore data Membrane will access.
- If you need higher assurance, inspect the @membranehq/cli package source (or the repo referenced) and verify package provenance on npm/GitHub before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97ec0t2fya1e38591z2bn831984bc82
License
MIT-0
Free to use, modify, and redistribute. No attribution required.