Lint
v2.0.1Check code syntax, enforce style, and suggest auto-fixes with CI integration. Use when linting PRs, enforcing code style, detecting errors before merge.
⭐ 0· 335·1 current·1 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 name/description (linting, tracking, CI integration) align with the provided CLI behavior: recording lint/check/format actions and exporting reports. Required tools listed (bash and common Unix utils) match what the script uses; no unrelated credentials or services are requested.
Instruction Scope
SKILL.md and the bundled script confine actions to local logging and exports in ~/.local/share/lint/. There are no instructions to read arbitrary system config, exfiltrate data, or call external endpoints. Commands operate on the data directory and user-provided text.
Install Mechanism
There is no install spec (lowest install risk), but the package includes an executable script (scripts/script.sh). That script is straightforward and local-only, but users/agents will need to decide how it's invoked or installed into PATH. Inspect the script before making it executable.
Credentials
The skill requires no environment variables or credentials beyond standard HOME usage. The script writes and reads only from ~/.local/share/lint/ and does not access unrelated secrets or external services.
Persistence & Privilege
The skill persists user data under ~/.local/share/lint/, which is expected for a logging tool. always is false and it does not modify other skills or system-wide agent settings. Consider that logs will remain on disk until removed.
Assessment
This skill appears coherent and local-only: it logs linting actions to ~/.local/share/lint/, doesn't request credentials, and has no network calls. Before installing/using: (1) review scripts/script.sh to confirm behavior (it will be executed locally if you run it); (2) only make the script executable if you trust the source; (3) be aware it will create persistent logs in your home directory (remove them if desired); (4) if you want extra safety, run it in a non-privileged account or sandboxed environment. No immediate red flags were found.Like a lobster shell, security has layers — review code before you run it.
latestvk97areynmxvetr8zx9n0394a15834f3n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.