Adjudicated 57 static findings against a documentation-only SKILL.md that teaches an agent how to use the published `genlayer` npm CLI. All 50 external_commands findings are false positives: the scanner matched Markdown inline-code backticks and fenced code blocks, not real shell/Ruby command substitution. The single network finding is an inert faucet documentation link, and the 'sensitive' finding is a comment describing the legitimate `account import` CLI command, not a hardcoded secret. No scripts, no runtime code, and no data-exfiltration intent were found.
Most static external-command findings are Markdown documentation false positives, but several documented CLI actions are real state-changing or secret-handling risks. The highest concern is guidance around private keys and passwords in command-line workflows.
The account import section explicitly introduces private-key and keystore import flows. Handling these secrets in an AI-assisted shell workflow creates a real risk of key disclosure.
The skill recommends command-line password arguments and echoing a password into a signing command. These patterns can expose secrets through shell history, process listings, logs, or copied prompts.
The guidance directly shows non-interactive password handling for account import and deployment flows. The risk is clear even though the examples use placeholder values.
Capability review items (14)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This account-management block includes commands for account creation, private-key import, unlocking, and token transfer. These commands can expose key material or move funds if run without careful confirmation.
`account create`, `account import`, and `account send` accept `--password <password>` to skip intera
The text recommends non-interactive password arguments for account commands. Passwords in command arguments can appear in shell history, process listings, and logs.
This block instructs users to run a global npm installation for the GenLayer CLI. Installing global packages executes third-party package code and changes the host environment.
6. **Appeal if needed**: `genlayer appeal <txHash>` (re-run consensus)
The debugging workflow includes an appeal command as a possible next action. That command can change transaction handling by triggering validator re-evaluation.