Skip to content
Skills Library
Programming · Building & coding

jshell

/jshell

Use when running Java snippets in JShell or using JShell as a Java REPL or scratchpad.

Author
Heapy ↗
Repository
kortex ↗
Licence
Apache-2.0
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when running Java snippets in JShell or using JShell as a Java REPL or scratchpad.

Original author description

Use when running Java snippets in JShell or using JShell as a Java REPL or scratchpad.

How it works

  1. Resolve the executable
  2. Start and use JShell
  3. Finish the session
Original SKILL.md headings · 44 lines, 312 words
SKILL.md preview
---
name: jshell
description: Use when running Java snippets in JShell or using JShell as a Java REPL or scratchpad.
---

# JShell

Run JShell in an agent-controlled terminal and own its lifecycle. Record its pid when it starts,
keep the terminal session, and do not finish the task until that session has exited.

## Resolve the executable

Run `jshell --version` before the first evaluation. On macOS, `/usr/bin/jshell` can be a launcher
that reports no Java runtime even when an SDK-managed JDK is installed. In that case, resolve an
installed JDK and use its absolute `bin/jshell` path for the rest of the task.

If a requested JShell option is uncertain, inspect that executable's `--help` or `--help-extra`.

## Start and use JShell

Start this command in a terminal with TTY enabled, replacing the final argument with the resolved
absolute path:

```sh
/bin/sh -c 'printf "JSHELL_PID=%s\n" "$$" >&2; exec "$1" --execution local --feedback concise' sh /absolute/path/to/jshell
```

Save both the returned terminal-session id and the printed `JSHELL_PID`. `exec` replaces the shell
with JShell without changing the pid, while `--execution local` keeps evaluation in that tracked
process.

Send Java snippets to the terminal session with a trailing newline. Poll a running session with an
empty write. A returned live-session id only means the command is still running; it does not prove
that JShell is waiting at a prompt.

## Finish the session

Never send `/exit`. When no more evaluation is needed:

1. From a separate terminal command, send `TERM` to the recorded numeric pid. For example, if
   JShell printed `JSHELL_PID=16438`, run `kill -TERM 16438`.
2. Poll the original terminal session with empty writes for at most five seconds.
3. If it has not exited after those five seconds, confirm that the same pid is still the tracked
   JShell process, send `KILL` to that pid, and poll the original session again until it exits.

Never abandon a live JShell terminal session. Do not use `pkill jshell` or `killall`; terminate only
the pid recorded for the current task.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named jshell.

Database snapshot: 13.11.2026 · package version 7d3b2e393c52 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cli-controller
    Use when controlling interactive CLI applications, debugging with pdb/gdb/jshell, spawning Claude Code instances, or working with REPLs and long-running processes
  • 96java
    Guidelines for building Java base applications Triggers on: **/*.java
  • 95java-11-to-java-17-upgrade
    Comprehensive best practices for adopting new Java 17 features since the release of Java 11. Triggers on: ["*"]
  • 85julia-evaluation
    Activates when user asks to run, evaluate, or test Julia code in a persistent REPL session, or mentions Julia REPL, Julia session, or hot-reloading Julia changes.
  • 100rolldown-repl
    Use to encode or decode rolldown REPL share URLs — `repl.rolldown.rs/#…`, `rolldown-repl.netlify.app/#…`, or any URL whose hash is a base64-encoded rolldown REPL payload. Decode whenever such a URL appears in the conversation (commonly in GitHub issues with a "minimal…
  • 100rolldown-repl
    Use to encode or decode rolldown REPL share URLs — `repl.rolldown.rs/#…`, `rolldown-repl.netlify.app/#…`, or any URL whose hash is a base64-encoded rolldown REPL payload. Decode whenever such a URL appears in the conversation (commonly in GitHub issues with a "minimal…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.