Applicantstack

v1.0.0

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

0· 46·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions: the skill instructs the agent to use the Membrane CLI to connect to ApplicantStack and run actions or proxied API requests. Required capabilities (network, Membrane account) are consistent with that purpose.
Instruction Scope
SKILL.md tells the user/agent to install and run the Membrane CLI, perform OAuth browser logins, create connections, run actions, and (optionally) proxy arbitrary ApplicantStack API requests via Membrane. This stays within the stated integration scope but explicitly routes data and credentials through Membrane's service — users should be aware their ApplicantStack data and API traffic will flow through that third-party service.
Install Mechanism
This is an instruction-only skill (no install spec), but the document directs users to install a public npm package (@membranehq/cli) globally. That is a reasonable and expected install for this integration, but it means installation happens outside the platform's managed install flow and will write a global binary to the host.
Credentials
No environment variables, secrets, or system config paths are requested. The SKILL.md explicitly recommends using Membrane connections rather than asking for API keys locally, which is proportionate for the integration.
Persistence & Privilege
The skill does not request always: true, does not modify other skills or system-wide settings, and relies on user-initiated CLI installation and browser-based auth. Autonomous invocation remains allowed (platform default) but is not combined with elevated privileges in the skill.
Assessment
This skill appears coherent: it uses the Membrane CLI to handle auth and proxy ApplicantStack API calls rather than asking for local API keys. Before installing or using it, verify you trust Membrane (https://getmembrane.com and the @membranehq npm package): data and credentials will transit Membrane servers. Installing the CLI will add a global npm binary to your system; prefer reviewing the package on npm/GitHub and Membrane's privacy/security docs. If the applicant data is sensitive, confirm compliance with your org's data-handling policies and permissions for any connector you create.

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

latestvk97ded41wxtfdp70mnq4e4f4rx84eame

License

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

Comments