nr-micro-shell-integration
/nr-micro-shell-integration
Use when integrating, porting, configuring, or debugging nr_micro_shell command consoles, UART shell input, command tables, or tiny embedded CLI behavior
- Author
- easyzoom ↗
- Repository
- aix-skills ↗
- Licence
- MIT
- Last repository change
- 17.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when integrating, porting, configuring, or debugging nr_micro_shell command consoles, UART shell input, command tables, or tiny embedded CLI behavior
Original author description
Use when integrating, porting, configuring, or debugging nr_micro_shell command consoles, UART shell input, command tables, or tiny embedded CLI behavior
How it works
- Overview
- When To Use
- First Questions
- Integration Checklist
- Common Failures
- Verification
- Example
SKILL.md preview
--- name: nr-micro-shell-integration description: Use when integrating, porting, configuring, or debugging nr_micro_shell command consoles, UART shell input, command tables, or tiny embedded CLI behavior --- # nr_micro_shell Integration ## Overview Use this skill to integrate nr_micro_shell as a compact command console. Keep the first port minimal: verified character I/O, one read-only command, bounded buffers, and explicit handling for destructive commands. ## When To Use Use this skill when: - The user wants a tiny shell/CLI on an MCU and mentions nr_micro_shell. - Commands are not recognized, input is garbled, completion/history fails, or shell processing blocks firmware. - The target needs a lower-footprint alternative to larger embedded shells. Do not use this skill when raw UART is not proven. Use `embedded-serial-log-debug` first. ## First Questions Ask for: - Target MCU/RTOS/compiler and nr_micro_shell version/source. - Transport: UART, USB CDC, RTT, TCP, or custom stream. - Polling, interrupt, DMA, or task-based input model. - Command table/registration approach. - Maximum command length, argument count, and stack/RAM budget. - Whether shell is enabled in production builds. ## Integration Checklist 1. Verify raw I/O. Confirm single-character RX/TX before attaching shell parsing. 1. Configure buffers. Set command line, history, and output buffers within RAM limits. 1. Register one safe command. Start with `help`, `version`, or `status`. 1. Validate argument parsing. Commands must reject missing, too many, or invalid arguments. 1. Bound output. Avoid long blocking output that starves watchdogs or RTOS tasks. 1. Guard risky commands. Reset, erase, format, calibration, flash writes, or network writes need build guards or authentication. ## Common Failures - RX callback stores characters but shell process function is never called. - Command table is not linked or is optimized out. - Backspace/newline behavior mismatches terminal settings. - Long command output blocks system timing. - Debug shell remains enabled in production without restrictions. ## Verification Before claiming nr_micro_shell works: - State transport, scheduling model, buffer sizes, and command registration method. - Confirm raw RX/TX, `help`, one custom read-only command, invalid command, and argument error behavior. - Confirm risky commands are absent, disabled, or guarded. ## Example User: ```text 想用 nr_micro_shell 做一个串口调试命令行。 ``` Agent: 1. Asks for UART path, scheduler model, buffer size, and production policy. 1. Verifies raw serial, then registers `status`. 1. Tests command parsing and guards destructive commands.
Versions
The database has no other skills named nr-micro-shell-integration.
Database snapshot: 13.11.2026 · package version 31628b2b3a87 (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
- 100zoom-shell-integration
Use when integrating, porting, configuring, or debugging an embedded zoom-shell style command console, UART CLI, command parser, or tiny MCU shell - 100letter-shell-integration
Use when integrating, porting, configuring, or debugging letter-shell command shells, UART shell transport, command registration, RTOS shell tasks, or embedded debug consoles - 100spring-shell
Spring Shell for building interactive CLI applications. Covers @ShellComponent, @ShellMethod, input validation, tables, and command groups. USE WHEN: user mentions "spring shell", "@ShellComponent", "@ShellMethod", "CLI application Spring", "interactive shell", "command line… - 100shell-integration
Interactive shell/TTY integration with tmux session management, shell command execution, control-mode output capture with polling fallback, native cursor rendering, lazy scrollback, selection, paste handling, and inline editing. Use when working on shell integration, tmux… - 100copilot
Delegate shell command lookups and GitHub CLI (gh) tasks to GitHub Copilot CLI. Use for shell/gh command suggestions and explanations only — not for code review, security decisions, or architecture. - 100cli-development
Use when building command-line tools. Covers argument design, exit codes, streams and piping, progress output, configuration precedence, and behavior that respects the shell. Trigger on "build a cli for", "what exit code should this return", "make this tool work in a pipe",…