zoom-shell Integration
Overview
Use this skill when the user explicitly means an embedded zoom-shell style MCU command console. Because the name is ambiguous, first confirm this is an embedded shell library, not the Zoom desktop application or a security research reverse shell.
When To Use
Use this skill when:
- The user mentions
zoom-shell in the context of MCU firmware, serial CLI, UART shell, or embedded command parsing.
- A tiny shell has missing commands, broken argument parsing, blocking output, or unreliable serial input.
- The task involves command tables, help output, bounded buffers, terminal line endings, or production debug command guards.
Do not use this skill for Zoom meeting apps, desktop automation, reverse shells, or non-embedded security research.
First Questions
Ask for:
- The exact
zoom-shell repository or source package.
- Target MCU, compiler, RTOS/bare-metal runtime, and serial transport.
- Input model: polling, interrupt RX, DMA RX, RTOS queue, USB CDC, RTT, or TCP.
- Command registration method and current command list.
- Maximum command length, argument count, and stack/RAM limits.
- Whether shell commands are allowed in production firmware.
Integration Checklist
Confirm the library identity.
Verify the user-provided source is an embedded shell and not an unrelated Zoom project.
Prove raw transport.
Check RX/TX before debugging shell parsing.
Configure bounded buffers.
Command line, argument list, history, and output buffers must fit RAM and reject overflow.
Register one read-only command.
Start with help, version, or status.
Validate argument parsing.
Test missing arguments, extra arguments, invalid numbers, and long input.
Guard dangerous commands.
Reset, erase, format, firmware update, calibration, and production-data commands need build guards or explicit authorization.
Common Failures
- Wrong library selected because
zoom-shell name was ambiguous.
- Shell receives characters but parser is not pumped from the main loop or task.
- Newline/backspace handling mismatches terminal settings.
- Command buffers overflow on pasted input.
- Debug commands remain enabled in release builds.
Verification
Before claiming zoom-shell integration works:
- State source repository/package, transport, scheduling model, and buffer limits.
- Confirm raw RX/TX,
help, one custom read-only command, invalid command, and long input handling.
- Confirm dangerous commands are absent, disabled, or guarded.
Example
User:
想把 zoom-shell 接到串口里做调试命令。
Agent:
- Confirms the source is an embedded shell library.
- Verifies raw UART RX/TX.
- Registers
status and tests invalid/long commands before adding write commands.
1---2name: zoom-shell-integration3description: Use when integrating, porting, configuring, or debugging an embedded zoom-shell style command console, UART CLI, command parser, or tiny MCU shell4---56# zoom-shell Integration78## Overview910Use this skill when the user explicitly means an embedded `zoom-shell` style MCU command console. Because the name is ambiguous, first confirm this is an embedded shell library, not the Zoom desktop application or a security research reverse shell.1112## When To Use1314Use this skill when:1516- The user mentions `zoom-shell` in the context of MCU firmware, serial CLI, UART shell, or embedded command parsing.17- A tiny shell has missing commands, broken argument parsing, blocking output, or unreliable serial input.18- The task involves command tables, help output, bounded buffers, terminal line endings, or production debug command guards.1920Do not use this skill for Zoom meeting apps, desktop automation, reverse shells, or non-embedded security research.2122## First Questions2324Ask for:2526- The exact `zoom-shell` repository or source package.27- Target MCU, compiler, RTOS/bare-metal runtime, and serial transport.28- Input model: polling, interrupt RX, DMA RX, RTOS queue, USB CDC, RTT, or TCP.29- Command registration method and current command list.30- Maximum command length, argument count, and stack/RAM limits.31- Whether shell commands are allowed in production firmware.3233## Integration Checklist34351. Confirm the library identity.36 Verify the user-provided source is an embedded shell and not an unrelated Zoom project.37381. Prove raw transport.39 Check RX/TX before debugging shell parsing.40411. Configure bounded buffers.42 Command line, argument list, history, and output buffers must fit RAM and reject overflow.43441. Register one read-only command.45 Start with `help`, `version`, or `status`.46471. Validate argument parsing.48 Test missing arguments, extra arguments, invalid numbers, and long input.49501. Guard dangerous commands.51 Reset, erase, format, firmware update, calibration, and production-data commands need build guards or explicit authorization.5253## Common Failures5455- Wrong library selected because `zoom-shell` name was ambiguous.56- Shell receives characters but parser is not pumped from the main loop or task.57- Newline/backspace handling mismatches terminal settings.58- Command buffers overflow on pasted input.59- Debug commands remain enabled in release builds.6061## Verification6263Before claiming zoom-shell integration works:6465- State source repository/package, transport, scheduling model, and buffer limits.66- Confirm raw RX/TX, `help`, one custom read-only command, invalid command, and long input handling.67- Confirm dangerous commands are absent, disabled, or guarded.6869## Example7071User:7273```text74想把 zoom-shell 接到串口里做调试命令。75```7677Agent:78791. Confirms the source is an embedded shell library.801. Verifies raw UART RX/TX.811. Registers `status` and tests invalid/long commands before adding write commands.
easyzoom