Portcheck
v2.0.3Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Portcheck concepts, best practices, and implementation patterns.
⭐ 0· 116·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
The skill is advertised as a reference/cheatsheet for Portcheck and the included SKILL.md and scripts produce plain-text documentation for the listed commands. There are no unexpected binaries, credentials, or external services required that would contradict the stated purpose.
Instruction Scope
SKILL.md explicitly states no external API calls or network access. The provided script prints documentation via heredocs and does not read files, environment variables, or network resources. Minor mismatches exist (script VERSION shows 2.0.2 while metadata is 2.0.3, and the cheatsheet mentions a 'troubleshooting' command that isn't implemented), but these are quality/incoherence issues rather than security concerns.
Install Mechanism
There is no install spec; the skill is instruction-only plus a small bash script. Nothing is downloaded or written to disk by an installer step, and no external package installs are declared.
Credentials
The skill requires no environment variables, no credentials, and no config paths. The runtime script does not attempt to read or use environment variables or secrets.
Persistence & Privilege
The skill is not forced-always, does not request permanent presence, and does not modify other skills or system-wide settings. It contains only a runnable script that outputs static documentation.
Assessment
This skill is self-contained documentation and appears safe: it prints help text and does not access network or secrets. Before installing or enabling: (1) review the bundled scripts yourself (they're small and readable) and run them locally in a sandbox if you want to verify behavior; (2) note the minor inconsistencies (script VERSION differs from metadata and a 'troubleshooting' command is referenced but not implemented) which are likely quality issues not security risks; (3) if you plan to let an autonomous agent invoke skills, remember this one is harmless but always consider whether any skill should be allowed to run commands in your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk9753jagjccjma2nrw1n6j4z3583gjkx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.