Lint checks code for syntax errors, enforces style, suggests fixes, manages configs, and supports CI integration with local processing.
Security Analysis
high confidenceThe skill's code, instructions, and runtime behavior are consistent with a small local linter utility that stores data under the user's home; nothing requested or executed appears disproportionate to its stated purpose.
Name/description (linting, config management, CI integration) matches the provided script and SKILL.md: the script implements run/list/add/status/export commands and stores data in a per-user data directory.
SKILL.md and the script are narrowly scoped to local lint tasks and local data storage. One minor omission: the script invokes python3 for JSON export but the metadata/SKILL.md do not declare a python requirement or required binaries; this is low-risk but a slight mismatch in declared runtime requirements.
No install spec is provided (instruction-only with a small included script). Nothing is downloaded or written to unexpected system locations; the script creates a per-user data directory under XDG_DATA_HOME or $HOME.
The skill requires no credentials or special environment variables. It reads XDG_DATA_HOME/$HOME to determine its data directory, which is proportional to its purpose.
The skill does not request persistent platform privileges (always:false). It only creates and updates files in a user-writable data directory (~/.local/share/lint), which is expected behavior for a local CLI tool.
Guidance
This skill appears to be a small, local linter implemented as a bash script that stores its data under ~/.local/share/lint and does not make network calls or request credentials. Before installing or running: (1) inspect the script (you already have it) and confirm you are comfortable with files being created/updated in ~/.local/share/lint (history.log and items.txt); (2) be aware that exporting JSON invokes python3—ensure python3 is available and from a trusted installation; (3) because the source/homepage is unknown, run it in a sandbox or non-production environment first if you have concerns; and (4) avoid adding sensitive data via the tool (anything you add via lint add will be stored in the data files). Overall the package is coherent with its stated purpose.
Latest Release
v1.0.1
Standards compliance: unique content, no template text
More by @xueyetianya
Published by @xueyetianya on ClawHub
