Capistrano
v3.0.2Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Capistrano concepts, best practices, and implementation patterns.
⭐ 0· 274·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
Name/description (Capistrano reference) match the provided artifacts: SKILL.md documents reference commands and the included scripts output static help/docs. There are no unexpected credentials, binaries, or external services requested.
Instruction Scope
SKILL.md explicitly states no external API calls or network access. The runtime script (scripts/script.sh) only prints heredoc documentation and handles a simple command dispatch; it does not read files, environment variables, or call external endpoints. Minor implementation quirk: some heredocs are single-quoted so $VERSION won't expand in help text, but that's a harmless bug, not scope creep.
Install Mechanism
No install spec is provided (instruction-only), so nothing is downloaded or written to disk by an installer. The only code shipped is a small local script; no external installers or archives are referenced.
Credentials
The skill declares no required environment variables, primary credential, or config paths, and the script does not access environment variables or secrets. Requested access is proportional (none).
Persistence & Privilege
always is false and the skill does not request persistent/system-wide changes. It does not modify other skills or system configuration. Autonomous invocation is allowed by default but is not combined with any concerning privileges or credentials.
Assessment
This skill appears to be a harmless, local reference tool: it prints static documentation and does not require keys, network access, or elevated privileges. If you install or enable it, you may want to: (1) inspect scripts/script.sh yourself (it's short and readable) before running; (2) be aware that the agent could call the script when the skill is invoked; and (3) if you prefer, run the script in a sandbox or inspect it locally rather than granting any automated platform-wide permissions. No red flags were found.Like a lobster shell, security has layers — review code before you run it.
latestvk972sh75jvyacpc3zd5c26tfzx83hj35
License
MIT-0
Free to use, modify, and redistribute. No attribution required.