Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AppDeploy
v1.0.0Deploy web apps with backend APIs, database, file storage, AI operations, authentication, realtime, and cron jobs. Use when the user asks to deploy or publis...
⭐ 0· 18·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes a full app deployment service (build, upload, status, versions) which is coherent with the 'AppDeploy' name. However the registry metadata claims no required environment variables while the SKILL.md explicitly declares and depends on SKILLBOSS_API_KEY; this mismatch is an integrity problem (declaration vs runtime instructions).
Instruction Scope
Runtime instructions direct the agent to send app files, diffs, and deployment metadata to an external HTTP API (https://api.heybossai.com/v1/pilot). That is expected for a deploy skill but is high-impact because arbitrary project files (source, configs) may be uploaded. The SKILL.md also includes tool semantics that give agents discretion about which files to include (src_glob, files[], diffs[]). There are also odd presentation rules (e.g., 'DO NOT display the "version" value to users') that are unexplained. Overall the instructions grant broad discretion to read and transmit project data to a third party.
Install Mechanism
Instruction-only skill with no install spec and no bundled code — lowest install risk. The SKILL.md relies on curl/Bash for HTTP calls; nothing is being downloaded or installed by the skill itself.
Credentials
SKILL.md requires a single credential SKILLBOSS_API_KEY to authenticate with the SkillBoss API, which is proportionate for an external deployment service. However the registry metadata lists no required env vars (contradiction). Requiring an API key that wasn't declared in the registry is suspicious because it prevents straightforward automated vetting and surprises the user with a credential requirement at runtime.
Persistence & Privilege
The skill is not marked always:true, does not request system config paths, and is user-invocable. Autonomous invocation is allowed (default) but not combined with other excessive privileges. No evidence it modifies other skills or system-wide settings.
What to consider before installing
This skill will send your app source and deployment metadata to a third-party service (SkillBoss / heybossai). Before installing: (1) confirm you trust the SkillBoss service and domain (verify company, privacy/storage policy, and where uploaded code will be stored/executed); (2) expect to provide SKILLBOSS_API_KEY — create a key with the least privilege possible or use a disposable/test account if you want to try it; (3) ask the publisher for clarity about the registry/manifest mismatch (registry lists no env vars, SKILL.md requires one) and confirm the canonical homepage/source repo; (4) do not use this skill with repositories or projects containing secrets (API keys, private keys, credentials) unless you have verified the external service's security and retention policies. If you cannot validate the endpoint, provenance, or privacy guarantees, treat this skill as untrusted and avoid uploading sensitive code.Like a lobster shell, security has layers — review code before you run it.
automationvk979fkdkaj7dbyj4h92q0tj0ph84rbb7deploymentvk979fkdkaj7dbyj4h92q0tj0ph84rbb7latestvk979fkdkaj7dbyj4h92q0tj0ph84rbb7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.