Appveyor
v1.0.2AppVeyor integration. Manage Projects, Accounts, Users. Use when the user wants to interact with AppVeyor data.
⭐ 0· 201·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 match the instructions: the SKILL.md consistently documents using the Membrane platform to interact with AppVeyor (list projects/users, start builds, proxy requests). It does not request unrelated credentials or system access.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, logging in via browser, creating a Membrane connection to AppVeyor, listing/running actions, or using Membrane's proxy. The instructions do not ask the agent to read unrelated files, export environment variables, or exfiltrate data outside the Membrane/AppVeyor flow.
Install Mechanism
There is no formal install spec in the registry metadata (instruction-only skill). The SKILL.md tells the user to run `npm install -g @membranehq/cli`, which is a public-registry global npm install — expected for a CLI but carries the usual npm/global-install considerations (trust the package, avoid running as root).
Credentials
The skill declares no required env vars or credentials. Authentication is delegated to Membrane (browser login / connector flow). This is proportionate to the task, though it does mean the user must trust Membrane with AppVeyor credentials/session tokens.
Persistence & Privilege
Skill metadata does not request persistent privileges (always:false). The only persistent change the instructions suggest is installing a CLI tool (global npm install), which is reasonable for a CLI-driven integration and is performed outside the agent runtime.
Assessment
This skill is an instruction-only integration that uses the Membrane CLI to talk to AppVeyor and does not request local secrets. Before installing/using it: 1) Verify you trust the @membranehq package (check the official repo and npm publisher) and avoid running npm installs as root; 2) Understand that Membrane will hold and proxy AppVeyor credentials — review Membrane's privacy/security and the connector permissions; 3) If you prefer not to install a global CLI, consider using a user-level install or a container/sandbox; 4) When using the connector, restrict AppVeyor permissions to the minimum required and review any actions that can delete projects/users.Like a lobster shell, security has layers — review code before you run it.
latestvk97eabn65z8gmvg01k4ktvg93h842kyd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.