terminal

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Bidirectional interactive terminal session tool for serial port terminals, SSH interactive shells, local shells, device consoles, AT/CLI menus, and interactive debugging that requires context retention; Triggered when users mention interactive terminals, serial port terminals, SSH terminals, opening shells, continuing to read output after sending commands, maintaining sessions, post-login operations, or menu-driven command lines, and also supports explicit invocation via /terminal.

11installs

Sourcezhinkgit/embeddedskills

Added on2026-05-27

NPX Install

npx skill4agent add zhinkgit/embeddedskills terminal

SKILL.md Content (Chinese)

View Translation Comparison →

Terminal — Bidirectional Interactive Terminal Session

Unified encapsulation of bidirectional interactive sessions for serial ports, SSH, and local shells. It fills the gap between

serial

's "monitoring/sending are separate commands" and

ssh

's "remote commands are mostly one-time executions": Use this skill when the target requires maintaining login status, menu status, REPL status, or device CLI context.

Positioning

```
serial
```
: Scanning, monitoring, one-time sending, logging, Hex viewing.
```
ssh
```
: OpenSSH configuration, remote commands, file transfer, tunneling.
```
terminal
```
: Maintain a sustainable read-write interactive session, and drive subsequent judgments through
```
send/read
```
.

Configuration

Environment-level Configuration (

config.json

)

The environment-level configuration for the terminal skill is currently an empty object

{}

. Key parameters for interactive terminals are usually bound to specific sessions, and are preferably passed explicitly via the

start

command to avoid misconnecting devices or misusing credentials.

Session State (

.embeddedskills/state.json

)

The runtime state of background sessions is saved to the workspace's

.embeddedskills/state.json

, using the

terminal_sessions

field to record session names, backends, PIDs, TCP control ports, and log paths.

Parameter Priority

CLI Parameters (
```
--port
```
,
```
--baudrate
```
,
```
--host
```
,
```
--name
```
, etc.) - Highest priority

Session State (

terminal_sessions

already started in

.embeddedskills/state.json

)

Default Values - Lowest priority

Subcommands

Subcommand	Purpose	Risk
`start`	Start a background interactive session	Medium
`list`	List existing sessions	Low
`status`	Query the status of a single session	Low
`send`	Write text or Hex data to the session	Medium
`read`	Read and clear the session output buffer	Low
`attach`	Access the session in foreground line mode	Medium
`stop`	Stop the session and clean up state	Medium

Backends

Backend	Applicable Scenarios	Dependencies
`serial`	MCU UART console, AT commands, Bootloader menus, board CLI	`pyserial`
`ssh`	Linux development board interactive shells, continuous operations after login	OpenSSH client
`local`	Local temporary shells, REPL, CLI program interaction	Python standard library

Script Invocation

All scripts are located in the

scripts/

directory of the skill, and can be called directly via

python

. Command examples are based on the current skill directory.

bash

# Start serial terminal
python scripts/terminal_session.py start serial --port COM11 --baudrate 115200 --name board

# Start SSH terminal, use Host alias from ~/.ssh/config
python scripts/terminal_session.py start ssh --host 1380-P904 --name devboard

# Start local Shell
python scripts/terminal_session.py start local --name local-shell

# Send a command line with appended CRLF
python scripts/terminal_session.py send board "help" --crlf

# Read output, wait up to 1 second
python scripts/terminal_session.py read board --timeout 1

# Access in foreground line mode
python scripts/terminal_session.py attach board

# Query and stop
python scripts/terminal_session.py list
python scripts/terminal_session.py status board
python scripts/terminal_session.py stop board

Session State Details

Session metadata is saved to the workspace:

text

.embeddedskills/state.json

Recorded using the

terminal_sessions

field:

json

{
  "terminal_sessions": {
    "board": {
      "backend": "serial",
      "tcp_port": 23145,
      "pid": 1234,
      "started_at": "2026-05-26T10:00:00+08:00"
    }
  }
}

Background process logs are saved to:

text

.embeddedskills/logs/terminal/

Output Format

Scripts output JSON by default:

json

{
  "status": "ok",
  "action": "read",
  "summary": "Read 42 bytes",
  "details": {
    "session": "board",
    "text": "help\r\n..."
  }
}

Error output:

json

{
  "status": "error",
  "action": "send",
  "error": {
    "code": "session_unreachable",
    "message": "Session unreachable, may have exited"
  }
}

Operation Process

Determine whether interactive state retention is truly needed; if it's just a one-time remote command, prioritize using
```
ssh
```
; if it's just serial port log capturing, prioritize using
```
serial
```
.
Select the backend: use
```
serial
```
for serial consoles,
```
ssh
```
for remote shells, and
```
local
```
for local interactive programs.
After
```
start
```
, first use
```
read --timeout 1
```
to get the startup banner, login prompt, or shell prompt.
After each
```
send
```
, use
```
read --timeout <seconds>
```
to observe feedback before deciding the next step.
Execute
```
stop
```
after completion to avoid background processes occupying serial ports, SSH connections, or local shells for long periods.

Core Rules

Do not automatically guess serial ports, baud rates, SSH Hosts, or login credentials.
Do not actively send any commands that change device status when the purpose is unclear.
Multiple sessions must use different
```
--name
```
to avoid output confusion.
```
read
```
will clear the current output buffer; important output needs to be recorded in the final reply promptly.
```
attach
```
is line mode, not equivalent to full TTY/raw mode; when full-screen programs, vim, top, or interactive password input are needed, prioritize letting users use real terminal tools.
Serial sessions will occupy the physical serial port exclusively; if sharing the port with external serial tools is needed, first use the mux capability of the
```
serial
```
skill.
The SSH backend uses Host aliases from
```
~/.ssh/config
```
; configuration of hosts, jump servers, and file transfer are still handled by the
```
ssh
```
skill.
Retain real errors when failures occur: do not swallow errors such as port occupation, missing
```
pyserial
```
, non-existent
```
ssh
```
, unresolvable Host aliases, exited processes, etc.

terminal

NPX Install

Tags

SKILL.md Content (Chinese)

Terminal — Bidirectional Interactive Terminal Session

Positioning

Configuration

Environment-level Configuration (
`config.json`
)

Session State (
`.embeddedskills/state.json`
)

Parameter Priority

Subcommands

Backends

Script Invocation

Session State Details

Output Format

Operation Process

Core Rules

terminal

NPX Install

Tags

SKILL.md Content (Chinese)

Terminal — Bidirectional Interactive Terminal Session

Positioning

Configuration

Environment-level Configuration (config.json)

Session State (.embeddedskills/state.json)

Parameter Priority

Subcommands

Backends

Script Invocation

Session State Details

Output Format

Operation Process

Core Rules

Environment-level Configuration (
`config.json`
)

Session State (
`.embeddedskills/state.json`
)