F java-switch
(no description)
- Safety 60%
- Quality 40%
- Tests bonus
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.
How to improve
- Add a description to the frontmatter: without it the skill can never trigger.
- Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
- Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.
Guard findings · 9
✓ No critical or high findings
Medium and low: 9
-
medium Dangerous commands
cmd-shell-rcscripts/switch-java.sh:65Writes to a shell startup fileecho "💾 步骤 6: 持久化配置到 ~/.zshrc..."
-
medium Dangerous commands
cmd-shell-rcscripts/switch-java.sh:70Writes to a shell startup fileecho "⚠️ 检测到 ~/.zshrc 中已有 JAVA_HOME 配置"
-
medium Dangerous commands
cmd-shell-rcscripts/switch-java.sh:74Writes to a shell startup filesed -i '' 's/^export JAVA_HOME=\$(\/usr\/libexec\/java_home/# &/' ~/.zshrc 2>/dev/null || true
-
medium Dangerous commands
cmd-shell-rcscripts/switch-java.sh:78Writes to a shell startup fileecho "" >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcscripts/switch-java.sh:79Writes to a shell startup fileecho "$ZSHRC_ENTRY" >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:68Writes to a shell startup fileecho '' >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:69Writes to a shell startup fileecho '# Java <version> configuration' >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:70Writes to a shell startup fileecho 'export JAVA_HOME=$(/usr/libexec/java_home -v <version>)' >> ~/.zshrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:71Writes to a shell startup fileecho 'export PATH=$JAVA_HOME/bin:$PATH' >> ~/.zshrc
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Lint
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process maturity 49/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 785 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 18 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (10 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.