Linecount
v2.0.3Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Linecount concepts, best practices, and implementation patterns.
⭐ 0· 137·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 name/description (Linecount reference for devtools) matches the provided files: SKILL.md documents reference commands and scripts/script.sh prints the same reference content. No unrelated binaries, credentials, or services are requested.
Instruction Scope
SKILL.md instructs the agent to output plain-text documentation with no external calls; the shipped script implements only heredoc outputs and local echo/cat operations. Minor documentation inconsistencies exist (e.g., quickstart mentions "Required tools and access credentials" generically, cheatsheet references a 'troubleshooting' command while the script uses 'debugging', and the script VERSION is 2.0.2 vs metadata 2.0.3) — these are clarity issues, not evidence of malicious behavior.
Install Mechanism
There is no install specification and no downloads; the skill is instruction-only with an included shell script. That is low-risk: nothing is written to disk by an installer beyond the existing files in the skill package.
Credentials
The skill declares no required environment variables, no credentials, and the script does not read environment variables or config paths. Requested environment access is proportional (none) to the stated purpose.
Persistence & Privilege
The skill does not request always:true and does not modify system or other skill configurations. It is user-invocable and can be invoked autonomously (platform default) but there are no elevated persistence or privilege requests in the package.
Assessment
This skill appears to be a benign local reference: it prints documentation and does not use network calls or credentials. Before installing, you can (1) inspect the included scripts (scripts/script.sh) yourself — it only prints heredoc text and uses standard shell builtins, (2) note the minor doc issues (version mismatch and a small command-name discrepancy) which are non-malicious but worth fixing, and (3) run the script in a safe environment if you want to verify behavior. If you store sensitive environment variables in your agent environment, these are not required by this skill, but it's good practice to avoid running unfamiliar skills without reviewing their files first.Like a lobster shell, security has layers — review code before you run it.
latestvk972r49tc0wyr11bqd3rsndtyh83hb0y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.