Deployer
v2.0.3Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Deployer concepts, best practices, and implementation patterns.
⭐ 0· 122·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is presented as a read-only reference for 'Deployer' concepts and its declared requirements (no env vars, no binaries, no network) match that purpose. The included script simply prints heredoc documentation. Minor inconsistencies in reported version strings exist (registry: 2.0.3, SKILL.md: 2.0.2, script VERSION: 2.0.1) but these are implementation/metadata issues, not indicators of malicious behavior.
Instruction Scope
SKILL.md explicitly states commands produce plain-text via heredoc and require no network or credentials. The runtime script (scripts/script.sh) only emits static documentation via heredocs and does not read external files, environment variables, or call external endpoints. No broad or vague instructions are present.
Install Mechanism
There is no install specification (instruction-only plus a small helper script). Nothing is downloaded or extracted and no third-party packages are installed.
Credentials
The skill requests no environment variables or credentials and the documented functionality does not require any. There are no environment accesses in the script.
Persistence & Privilege
always:false and no installation or configuration changes are requested. The skill does not attempt to modify other skills or system-wide agent settings.
Assessment
This skill appears to be a simple, local reference tool that prints documentation; it does not request credentials or network access. Before installing or executing: (1) if you plan to run the included script, inspect it (already done) and run it in a restricted environment if you prefer; (2) note minor metadata/version mismatches (harmless but worth noting); (3) avoid granting additional credentials or elevated permissions — none are needed. Overall low risk, but treat unknown third-party code cautiously and run in a sandbox if you have any doubt.Like a lobster shell, security has layers — review code before you run it.
latestvk97dgdbd7era7xkrvg92c0ewts83hbdr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.