CC near-tools
NEAR Protocol CLI installation and setup guide. Use when: (1) User asks how to install NEAR CLI, (2) User needs help setting up near-cli-rs, (3) User wants to verify NEAR CLI installation, (4) User needs to install near-cli-rs, (5) user wants to use near cli to perform any action on the blockchain. AGENTS MUST ALWAYS get the absolute path of the 'near' binary before execution.
NEAR Protocol CLI installation and setup guide.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 8
✓ No critical or high findings
Medium and low: 8
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:42Pipe-to-shell installer from a well-known host (still executes remote code)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
-
medium Dangerous commands
cmd-shell-rcREADME.md:130Writes to a shell startup fileecho 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.bashrc
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:27Pipe-to-shell installer from a well-known host (still executes remote code)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
-
medium Dangerous commands
cmd-shell-rcSKILL.md:40Writes to a shell startup fileecho 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.bashrc # For bash
-
medium Dangerous commands
cmd-shell-rcSKILL.md:41Writes to a shell startup fileecho 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.zshrc # For zsh
-
medium Risky intent
intent-wallet-secretsSKILL.md:178Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetIf you have a seed phrase or key:
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:240Pipe-to-shell installer from a well-known host (still executes remote code)curl --proto '=https' --tlsv1.2 -LsSf --connect-timeout 30 --max-time 300 https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:260Pipe-to-shell installer from a well-known host (still executes remote code)curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/near-cli-rs/releases/latest/download/near-cli-rs-installer.sh | sh
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (near-tools) differs from the folder (near-cli-tools)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 20 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1572 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 379: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.