SkillsAdd

smithery/creatifcoding

renode-for-tmnl

Renode practices for TMNL with tmux, UART sockets, telemetry, and guardrails.

Installation

$ npx skills add smithery/creatifcoding --skill renode-for-tmnl
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/creatifcoding · top by installs.

npx skills add smithery/creatifcoding
ux-interaction-patterns 0 tmnl-submodule-exploration 0 tmnl-registry-patterns 0 tmnl-component-tiers 0 streams-playground-system 0 spike-testing 0 research-council 0 research-cascade 0 react-hook-composition 0 react-compound-components 0

Browse all from smithery/creatifcoding

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Write

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,487 B
  • docs SUMMARY.md 100 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Renode for TMNL

When to Use

  • You need Renode setup, UART integration, or telemetry simulation.
  • You want a headless tmux workflow with UART and monitor panes.
  • You are writing or running .resc scripts for Renode.

Canonical Sources

  • Renode UART integration docs (CreateServerSocketTerminal, connector Connect).
  • TMNL scripts: embedded/renode/scripts/renode-init.sh.
  • Renode scripts: embedded/renode/nrf52840/nrf52840-telemetry.resc.

The Only Supported TMNL Path (Current)

Renode (headless) -> UART socket (TCP) -> nc (tmux pane) -> telemetry ingest

We use TCP UART sockets (not PTY) to allow nc everywhere.

Decision Trees

UART Exposure

Need UART access?
├─ Want nc everywhere?  -> CreateServerSocketTerminal (MANDATORY)
└─ Want PTY tooling?    -> CreateUartPtyTerminal (DO NOT for TMNL)

Renode Launch Mode

Running inside tmux?
├─ Yes -> renode-init.sh (MANDATORY)
└─ No  -> renode --disable-gui -e 'i @script.resc' (ALLOWED)

DO NOTs (Strict)

  • DO NOT use PTY UART for TMNL. Use TCP sockets + nc.
  • DO NOT start Renode with GUI when running in tmux.
  • DO NOT rely on ad-hoc commands. Use .resc scripts.
  • DO NOT mix registries or ports without documenting overrides.

Guardrails (Mandatory)

  • Always pass --disable-gui for headless runs.
  • Always expose UART with CreateServerSocketTerminal.
  • Always use connector Connect <uart> <socket>.
  • Always pin ports in the script (default: 5501).

Highly Suggested

  • Keep Renode in tmux session tmnl-renode.
  • Keep three windows: renode, uart, console.
  • Use nc for both UART and monitor.

Standard Commands

Start headless Renode + UART + monitor in tmux:

embedded/renode/scripts/renode-init.sh

Attach:

tmux attach -t tmnl-renode

UART socket (default):

nc 127.0.0.1 5501

Monitor socket (default):

nc 127.0.0.1 1234

Pitfalls

  • If UART appears silent, ensure firmware is loaded and connector Connect is present.
  • If nc shows no output, check Renode monitor for UART traffic.
  • If multiple Renode sessions run, port conflicts will be silent. Use one session.

Files to Edit

  • embedded/renode/nrf52840/nrf52840-telemetry.resc
  • embedded/renode/scripts/renode-init.sh
  • embedded/renode/README.md