Console Log Checker
v1.0.0Checks specified directory for console.log statements, excluding common folders, and reports file locations and line previews of occurrences.
⭐ 0· 91·1 current·1 all-time
by@sy724
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md instructions: the skill's stated goal is to locate console.log statements and the instructions only require searching files under a given path. There are no unrelated environment variables, binaries, or install steps.
Instruction Scope
Runtime instructions tell the agent to use a Grep tool to search for `console\.log` and to exclude common directories by default. The instructions operate on local files under the provided path (defaults to CWD) and do not direct data to external endpoints or request unrelated system credentials. Note: because it reads files in the given path, avoid running it with a path that includes sensitive system or home directories.
Install Mechanism
No install spec is present and no code files are bundled. This is the lowest-risk model for an agent skill: nothing is written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportional to its function of searching a codebase for console.log occurrences.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modification of other skills' configs. Autonomous invocation is allowed by default but not unusual; nothing in the skill asks for elevated privileges.
Assessment
This skill is coherent and straightforward. Before running it, ensure you set the path argument to the repository or folder you want scanned (avoid pointing it at system or home directories). Provide appropriate exclude patterns (e.g., node_modules, build, .git) if you want to avoid scanning large or sensitive folders. Because it searches local files, run it only in environments where the agent is allowed to read the target files. If you need an extra safety step, run the equivalent grep locally or in a disposable clone of the repo before granting the agent access.Like a lobster shell, security has layers — review code before you run it.
latestvk9716fxf8jajsje7wxfs61epex83mcwn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.