Checkr

v1.0.2

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

0· 115·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 name/description say 'Checkr integration' and the instructions exclusively describe using the Membrane CLI to connect to Checkr, discover actions, run actions, and proxy requests. The requested capabilities match the stated purpose.
Instruction Scope
SKILL.md confines runtime actions to installing/using the @membranehq/cli, running membrane login/connect/action/request commands, and handling JSON inputs. It does not instruct reading unrelated files, environment variables, or exfiltrating data to unknown endpoints; proxy requests target the Checkr API via Membrane as documented.
Install Mechanism
There is no registry install spec (skill is instruction-only). SKILL.md instructs a global npm install of @membranehq/cli. This is expected for a Membrane-based integration, but global npm installs carry the usual supply-chain/trust considerations—verify the package and publisher before installing.
Credentials
The skill declares no required environment variables or credentials. It relies on the Membrane account/connection flow (browser-based auth) to obtain access to Checkr, which is proportionate to its purpose. No unrelated secrets are requested.
Persistence & Privilege
always is false and the skill does not request persistent/always-on privileges or attempt to modify other skills or system-wide configuration. Normal autonomous invocation is allowed (platform default).
Assessment
This skill appears to do what it says: it uses the Membrane CLI to talk to Checkr. Before installing or running it, verify you trust the @membranehq/cli package and the Membrane service (review the npm package page and vendor site), because installing the CLI gives that tool the ability to act on your behalf and access Checkr data once you connect. Be aware that connecting grants Membrane access to the Checkr account's data (potentially sensitive PII), so authorize only accounts and scopes you intend. If you prefer not to install a global npm package, consider running the CLI via npx or in a contained environment.

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

latestvk978nk5zjyth86mtv9a6q675s98430q2

License

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

Comments