labwired-core

Name: labwired-core Review
Item: labwired-core
Rating: 2.8
Author: Aaron Matthews

Skill Development Usable

Works inClaude Code

Usable Scanned — metadata only

Deterministic firmware simulation reduces embedded development cycles and debugging time by enabling safe testing of ARM and RISC-V code without physical har…

Deterministic firmware simulator for ARM Cortex-M and RISC-V — with hardware-validated parity

Simulate ARM Cortex-M firmware execution to identify bugs before hardware testing
Validate RISC-V code behavior against actual processor specifications deterministically
Test embedded software edge cases without physical hardware boards available

44 starsMIT (commercial OK)FreeQuick setup

Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Why it matters

Deterministic firmware simulation reduces embedded development cycles and debugging time by enabling safe testing of ARM and RISC-V code without physical hardware. Hardware-validated accuracy ensures simulation results reliably predict real-world behavior.

Best for

Embedded systems teams developing ARM Cortex-M or RISC-V firmware needing fast iteration before hardware deployment.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://github.com/w1ne/labwired-core

By w1ne

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → Plugins → Add plugin. Search and click Install. Skills work in Claude Code only.

Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.

Command

claude plugins install w1ne/labwired-core

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me simulate ARM Cortex-M firmware execution to identify bugs before hardware testing

CostFree

Trust Signals Auto-scanned

Stars44Last updated2026-08-03LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-03 · scanner v1

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 44 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

3/5

Versatility

2/5

Reliability

3/5

Security

3/5

Overall score2.75 / 5.00 UsableEvaluatedAug 2026

Scored from trust signals (evidence-eval-v1): 44 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory