Async Interview

v1.0.2

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

0· 102·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 'Async Interview' and the SKILL.md explicitly instructs using Membrane to access Async Interview APIs. Requested actions (membrane CLI, connector IDs, proxy requests) are coherent with that goal.
Instruction Scope
Instructions remain within the stated domain (discover actions, run actions, or proxy requests through Membrane). They do instruct installing and running the Membrane CLI and performing browser-based login flows; these are expected for the described integration but will perform network auth and launch a browser or require a headless copy/paste flow.
Install Mechanism
The registry has no formal install spec, but the SKILL.md tells users to run `npm install -g @membranehq/cli`. That is a user-side global npm install (writes disk, may require privileges). This is not malicious but you should verify the npm package and source before installing.
Credentials
The skill declares no required env vars or secrets and explicitly advises not to ask users for API keys. It relies on Membrane to manage credentials server-side, which is consistent with its described behavior.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and allows normal autonomous invocation (platform default) but does not request system-wide changes or other skills' configs.
Assessment
This skill is coherent with its purpose, but before installing or using it: verify the Membrane CLI package (@membranehq/cli) on npm and its GitHub repository to ensure authenticity; be aware `npm install -g` will put a binary on your system (may require admin rights); the CLI will open a browser for auth (or emit a code for headless flows) and Membrane will manage credentials and proxy requests to Async Interview — review Membrane's privacy/security docs if you care about where your data/credentials are stored. If you prefer not to install global CLI tools, consider running the CLI in a confined environment or container. Finally, note the skill can be invoked by the agent (normal platform behavior); if you want to limit autonomous actions, adjust agent invocation settings.

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

latestvk97en2y1tq8ksdtj9k23a9797s842akv

License

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

Comments