Sailpoint
v1.0.2SailPoint integration. Manage data, records, and automate workflows. Use when the user wants to interact with SailPoint data.
⭐ 0· 91·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (SailPoint integration) align with the instructions: all runtime actions use the Membrane CLI to discover connectors, create connections, run actions, or proxy API requests to SailPoint. No unrelated services, credentials, or binaries are requested.
Instruction Scope
SKILL.md limits runtime activity to installing/using the Membrane CLI, performing browser-based login, running membrane commands (search/connect/action/request). It does not instruct reading arbitrary local files, environment secrets, or contacting unexpected endpoints beyond Membrane/SailPoint.
Install Mechanism
This is an instruction-only skill (no install spec). The README recommends installing @membranehq/cli via npm -g (or using npx). Installing a global npm package runs code from the npm registry, which is normal for CLIs but carries the usual risks—verify the package source and maintainer before installing.
Credentials
The skill declares no required env vars, no credentials, and no config paths. It explicitly delegates auth to Membrane, which is coherent for a connector-oriented integration.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears internally consistent: it tells the agent to use the Membrane CLI to access SailPoint and does not request additional credentials. Before installing/using it, verify the trustworthiness of Membrane and the @membranehq/cli package (check the npm package owner, GitHub repo, release history, and reviews). Prefer using npx for one-off runs if you want to avoid a global install. Confirm your organization's policy for delegating identity-access to third-party platforms (Membrane) and ensure least-privilege connector configuration—audit what SailPoint scopes/privileges the connector will be granted and avoid using on highly sensitive production data until reviewed.Like a lobster shell, security has layers — review code before you run it.
latestvk972ccv4t05wy87b8sv1bqras9842vzx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.