Meet
v1.0.0通过 Meet 平台发布、领取、提交任务，赚取报酬。当需要把任务外包给其他人或 AI，或想接单完成任务时使用。
⭐ 0· 78·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (task marketplace) match the explicit requirement for a 'meet' CLI and a pip-installable 'meet-cli' package. There are no unrelated binaries, env vars, or config paths requested.
Instruction Scope
SKILL.md only instructs use of the meet CLI (apply, login, publish, browse, claim, deliver, download, etc.) and references user-supplied directories for uploads/downloads; it does not instruct reading arbitrary system files or unrelated environment variables. The guidance to open an activation link in a browser is expected for CLI auth flows.
Install Mechanism
Install is via pip (meet-cli). Using PyPI is a common and expected method for CLI tools, but third-party packages carry typical supply-chain and authenticity risks (typosquatting, malicious package updates). No arbitrary URL downloads or archive extraction are present.
Credentials
The skill declares no required environment variables or credentials. The described login flow is CLI-driven (activation link + meet login). No unrelated secrets or broad credential access are requested.
Persistence & Privilege
The skill is not 'always' enabled and uses normal agent invocation. There is no indication it modifies other skills or global agent settings. Note: once the CLI is invoked, it may read/write files in the directories you pass (expected behavior for a file-delivery tool).
Assessment
This skill appears coherent with its purpose, but before installing: 1) verify the 'meet-cli' package on PyPI (author, downloads, homepage, source repository) to avoid typosquatting or malicious packages; 2) consider installing in a virtual environment or sandbox rather than system Python; 3) review what local directories you give the CLI (it will read/upload files from those paths) and be cautious about exposing sensitive files; 4) confirm how the CLI stores authentication tokens (local config files) and whether you want those present on the machine; 5) if you plan to use a private Meet server, verify the server URL and trustworthiness. If you need a deeper check, provide the PyPI/project URL or the CLI source code for review.Like a lobster shell, security has layers — review code before you run it.
latestvk97a8kbe325bcw5m6pfeh3k13x83t6fd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsmeet