CF junie
Install, update, authenticate, configure, and direct JetBrains Junie CLI in Junie-native ways on macOS or Linux shells. Use when a host agent should steer Junie iteratively toward an overall goal, especially when the host agent has broader context than Junie, Junie should carry out focused implementation/review work, or the task may benefit from Junie-accessible models not available to the host agent. Also use when asked to set up Junie, verify an existing install, create or adjust ~/.junie/config.json or project .junie/config.json, bootstrap a repo’s .junie layout, wire in skills/guidelines/MCP/model locations, prepare Junie for CI headless usage, or decide whether interactive Junie flows truly require headless-terminal-style PTY control. Trigger on limited host-agent command phrases such as /junie help, /junie status, /junie model, /junie usage, /junie bootstrap, and /junie dry-run.
As a process F 59/100 · Will not run — References files that are not bundled: scripts/install_junie.ps1
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
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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-execpolicy-bypassSKILL.md:118Runs PowerShell with execution policy bypassedpowershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\inst…ps1
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:124Runs PowerShell with execution policy bypassedpowershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\inst…ps1 -Reinstall
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:125Runs PowerShell with execution policy bypassedpowershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\inst…ps1 -Version 888.169
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:126Runs PowerShell with execution policy bypassedpowershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\inst…ps1 -Method winget
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:127Runs PowerShell with execution policy bypassedpowershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\inst…ps1 -Method npm
-
low Dangerous commands
cmd-pipe-to-shellreferences/junie-doc-notes.md:8Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host; quoted — discussed, not commanded)- macOS/Linux: `curl -fsSL https://junie.jetbrains.com/install.sh | bash`
vendor-hostquoted -
low Dangerous commands
cmd-pipe-to-shellreferences/junie-doc-notes.md:9Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host; quoted — discussed, not commanded)- Windows PowerShell: `powershell -NoProfile -ExecutionPolicy Bypass -Command "iex (irm 'https://junie.jetbrains.com/install.ps1')"`
vendor-hostquoted -
low Dangerous commands
cmd-execpolicy-bypassreferences/junie-doc-notes.md:9Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- Windows PowerShell: `powershell -NoProfile -ExecutionPolicy Bypass -Command "iex (irm 'https://junie.jetbrains.com/install.ps1')"`
quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5796 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/install_junie.ps1
Process rating: all ten parameters 59/100
- 0Tools and files. 1 referenced file(s) missing: scripts/install_junie.ps1
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 70Execution cost. Instruction body is 5796 tokens
- 85Steps. 122 steps, 3 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 17 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
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 897: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 122 items
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.