SkillAgentSearch skills...

TurboJedi

Turbo Vision viewer of the systemd journal, scriptable in Lua, with an MCP server for AI agents

Install / Use

claude mcp add cyanide-burnout -- npx -y github:cyanide-burnout/TurboJedi

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

84/100

Supported Platforms

Claude Code
Claude Desktop

Tags

Our assessment of TurboJedi

TurboJedi scores 84/100 on our quality scale, 2794th of 4,698 Development & Engineering skills we index.

Its MCP Server is 23 KB long, well organised into 16 sections with 20 code examples: a thorough specification that gives an agent plenty to work with.

It has 45 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
7/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so TurboJedi is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

TurboJedi compared with similar skills

All 4 of these similar skills score higher than TurboJedi; compare them before choosing.

SkillScoreStarsUpdatedFormat
TurboJedi (this skill)by cyanide-burnout8445todayMCP Server
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md

Frequently asked questions

How do I install TurboJedi?
Run claude mcp add cyanide-burnout -- npx -y github:cyanide-burnout/TurboJedi. The install tabs above show the steps for each supported agent.
Which AI agents does TurboJedi work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is TurboJedi safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is TurboJedi still maintained?
The repository was last updated today, so TurboJedi is actively maintained.

TurboJedi

Turbo Journald Interface (J[e]DI) — a Turbo Vision viewer of the systemd journal. Every window is a journal client of its own: its filter goes to the journal as a query, so a window of one unit or of errors only reads just those entries, while other windows follow the whole system next to it.

It is scriptable in Lua 5.4: plugins make the Actions menu of an entry and watch the journal as it comes, see PLUGINS.md. It is open to AI agents as well: turbojedi-mcp.py, a server of the Model Context Protocol, gives Claude Code, Codex or another agent the windows you have open, over SSH; the agent finds and points at entries on your screen, you act, see MCP.md.

Built on magiblot/tvision, libsystemd, PCRE2, Lua 5.4 and libcurl.

Three windows: the whole journal following, its warnings and errors paused with marked lines and 7 entries come meanwhile, and their timeline

Features

  • Windows with journals and filters of their own: journals of this machine, of every machine or of a directory, one mounted from another machine over SSH or NFS as well, levels, source (unit, identifier, command, transport, boot, user, machine, PID, any FIELD=VALUE), time range, and text, plain or a regular expression of PCRE2, to show or to leave out
  • Follows the tail, Space pauses; scrolling past the oldest line brings the older entries in. The title of every window tells it: ► follows, ‖ is paused, ‖ +12 has 12 entries come meanwhile; a click on the sign pauses or follows. A paused window that is full keeps its lines and marks, the new entries are counted and come in when it follows again
  • The newest entries at the bottom or on top, like journalctl --reverse, for every window of its own; the lines of a message stay under it, the title ends with ▲ or ▼ and a click on it turns the order
  • Columns to choose: date, time, level, host, unit, identifier, PID; UTC, milliseconds, wrapped messages, hidden heading, the newest on top
  • Highlighting of messages by rules: built-in ones for times, addresses, identifiers, paths, quoted text, key=value and the words that matter, or any rule file of grc; colors of the escape sequences a message comes with are shown under the rules, the rest of the sequences are taken out
  • Find with highlighting, next and previous, on into the older entries past the oldest line
  • Clone of a window with its lines, filter, selection and place: one stays where it is, the other goes elsewhere; a timeline is cloned with its counts, step and scale
  • List of the windows to go to, narrowed down by a filter
  • Go to a time, and every other window to the time of the selected line: what happened elsewhere at that moment
  • Details of an entry with all its fields, a field there opens a window narrowed to it
  • Actions of an entry by plugins in Lua 5.4: Alt-F10, A, F11, Shift-F10 or a right click opens the menu of what the plugins offer for it, each item named with its plugin. The plugins of the package only look: the status of the unit of the entry, its state told in the menu, its unit file and its process in top, the route, lookup, whois, ping and path of an address, a core dump in coredumpctl and gdb, a ban in fail2ban after a confirmation; the attacks on the SSH server in a watch, block devices, Asterisk, alerts and a chat are in the examples. Plugins ask with dialogs, run commands in the background, in a window or on the terminal, ask web services over HTTP, call services over D-Bus with typed values and keep sockets and timers going, see PLUGINS.md
  • Watches of plugins: entries of a filter as they come, a status and lines of each in a list, F12; Watch 1/3 * in the status line tells about new ones, an important one brings the list up with a bell
  • AI agents: every instance offers its workspace on the system bus, and turbojedi-mcp.py gives it to an agent such as Claude Code or Codex over SSH: the windows, the entry under the cursor, the marked entries, queries of the journal and the watches. The agent marks entries, puts the cursor on one, takes a window to a moment or opens one, the status line tells it; it runs nothing, the user acts. See MCP.md, the interface itself in DBUS.md
  • Selection with the keyboard or the mouse, copy to the clipboard (OSC 52 over SSH), export to a file
  • Timeline: entries of the filter of a window by intervals of time, errors, warnings and the rest stacked in a column per interval; a column takes every journal window to its time
  • Layouts: all windows with their filters, columns and places, saved to and opened from INI files; the last one comes back on the next start
  • Check for updates in the Help menu: asks GitHub for the latest release only when chosen, shows it with the command of the install script; nothing goes to the network otherwise. Its answer has the choice of a check on start, once a day and only about a newer release, kept in $XDG_CONFIG_HOME/turbojedi/update.ini; the first start without that file asks for the choice once, Yes or No

Installation

Ready packages of every release are on the releases page: Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04, Fedora 44, RHEL 9 and 10 (and their rebuilds), Amazon Linux 2023, openSUSE Tumbleweed and Leap 16 on amd64 and arm64, Arch Linux on amd64. GitHub Actions builds each of them in a container of its distribution. The script takes the one that fits:

curl -fsSL https://raw.githubusercontent.com/cyanide-burnout/TurboJedi/master/install.sh | sh

It asks for sudo when not run as root, TURBOJEDI_VERSION=0.6 before sh takes that release instead of the latest one. Run again, it updates TurboJedi and leaves it alone when that release is installed already. After an upgrade of the distribution it puts the package of the same release built for the new one; Check for updates tells about it as well. Raspberry Pi OS of 64 bits is Debian on arm64 and has packages; on 32 bits (armhf) TurboJedi builds from the sources. By hand:

sudo apt install ./turbojedi_<version>_<distribution>_<arch>.deb
sudo dnf install ./turbojedi-<version>-1.<dist>.<arch>.rpm
sudo zypper install --allow-unsigned-rpm ./turbojedi-<version>-1.<tumbleweed|leap16>.<arch>.rpm
sudo pacman -U turbojedi-<version>-1-x86_64.pkg.tar.zst

Alpine has no systemd, so there is no journal to show. Elsewhere TurboJedi builds from the sources.

Building

Debian packages: build-essential cmake pkg-config libsystemd-dev libncurses-dev libpcre2-dev liblua5.4-dev libcurl4-openssl-dev, libgpm-dev for the mouse in the Linux console, and grc for its rule files if they are wanted

git submodule update --init
make
sudo make install

A clone is updated with its submodule, a plain git pull leaves tvision where it was until git submodule update --init:

git pull --recurse-submodules
make

make builds tvision in Import/tvision/build first, and again what has changed in it after the submodule has moved. make install puts the executable to /usr/local/bin, the manual page to /usr/local/share/man/man1 and the plugins to /usr/local/share/turbojedi, PREFIX and DESTDIR move them. Without libgpm the build goes on, with the mouse in terminal emulators only; the mouse of the Linux console needs the gpm service running. libcurl serves Check for updates and the requests of plugins. Lua 5.4 is needed; distributions name its pkg-config module in their own ways, lua5.4, lua54 or lua, any of them of version 5.4 is taken.

About, --help and Check for updates link to the repository on GitHub the clone comes from, its origin, so a fork links to itself and checks its own releases. A copy without git or a clone of another host has none, make REPOSITORY= leaves it out on purpose and make REPOSITORY=https://github.com/owner/name names another one.

Debian package

sudo apt install debhelper
make deb

make deb builds turbojedi_<version>_<arch>.deb and its -dbgsym next to the directory of the project, with the files in /usr. The version comes from git describe the way the program shows it: v0.1-3-gabcdef becomes 0.1+3+gabcdef.

make deb DISTRIBUTION=amd64 builds for another architecture, with the cross compilers and the libraries of that architecture in place:

sudo dpkg --add-architecture amd64
sudo apt update
sudo apt install crossbuild-essential-amd64 libsystemd-dev:amd64 libncurses-dev:amd64 libpcre2-dev:amd64 libgpm-dev:amd64 libcurl4-openssl-dev:amd64 liblua5.4-dev:amd64

RPM package

sudo dnf install rpm-build gcc-c++ make cmake systemd-devel ncurses-devel pcre2-devel gpm-devel libcurl-devel lua-devel
make rpm

make rpm builds rpmbuild/RPMS/<arch>/turbojedi-<version>-1.<dist>.<arch>.rpm for Fedora, RHEL and Amazon Linux, with the version the same way. RHEL 9 and its rebuilds have lua-devel in CRB: sudo dnf config-manager --set-enabled crb. openSUSE takes the same packages from zypper with lua54-devel and gcc-PIE, gives no tag of its own and gets it by make rpm DIST=tumbleweed or DIST=leap16.

Arch Linux package

sudo pacman -S --needed base-devel cmake git pkgconf gpm curl lua54
make arch

make arch builds arch/turbojedi-<version>-1-<arch>.pkg.tar.zst with makepkg, as a user other than root.

Packages of a release

A tag v* makes GitHub Actions build all the packages and put them to its release. The notes of the release are the section of CHANGELOG.md for its version, written before the tag.

Usage

turbojedi [options] [FIELD=VALUE ...]

| Option | | |---|---| | -t, --identifier ID | entries of SYSLOG_IDENTIFIER | | -u, --unit UNIT | entries of a systemd unit, .service is assumed without a suffix | | -U, --user USER | entries of a user, by name or number | | -p, --priority LEVEL | entries up to LEVEL: emerg … debug or 0 … 7 | | -k, --kernel | kernel messages only | | -S, --since TIME | entries from TIME on | | --until TIME | entries up to TIME | | -b, --boot | entries of the current boot | | -D, --directory DIR | journal files of DIR in the first window | | -m, --merge | journals of every machine there are in the first window, like journalctl --merge: other machine IDs in /var/log/journal and /var/log/journal/remote of systemd-journal-remote | | -n, --lines N | history to start with, 1000 by default | | -r, --reverse | the newest entries on top in the first window, like journalctl --reverse | | -H, --highlight NAME | highlighting rules: builtin (default), off, a rule file of grc such as conf.log, or a path | | -c, --layout FILE | windows of a saved layout | | --clipboard-copy COMMAND | command of sh that takes copied lines on its standard input, over $TURBOJEDI_CLIPBOARD_COPY |

TIME is 2026-10-23 19:00[:00], 2026-10-23, 19:00, now, today, yesterday, tomorrow or a relative one as journalctl takes it: -1h, +30m, -1h 30min, -2days, 5min ago (us, ms, s, min, h, d, w, M, y and their longer names).

Reading the whole journal needs root or the systemd-journal group, others see their own entries only.

Copy (Ctrl-Ins, and Copy in the details) goes to the clipboard of the terminal by OSC 52 or to a clipboard tool of the desktop. A command of your own takes the lines instead, such as remote-copy.sh of RemoteClipboard that brings them home over an SSH socket:

export TURBOJEDI_CLIPBOARD_COPY="$HOME/remote-copy.sh"
turbojedi

When the command exits with an error or does not finish in 3 seconds, the clipboard of the terminal takes the lines as usual. Input lines of the dialogs keep the clipboard of Turbo Vision, pasting is up

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars45
CategoryDevelopment
Updated4h ago
Forks0

Languages

C++

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low1 info