
Adapter Scaffold
- 1 installs
- Updated July 25, 2026
- agodianel/firmware-replay-lab
adapter-scaffold is a Claude Code skill that scaffolds a new Python platform adapter for Firmware Replay Lab, including parser, tests, and log fixtures.
About
adapter-scaffold generates a new platform adapter for Firmware Replay Lab so it can support an additional board or framework such as ESP32 or STM32. It creates a Python adapter module with a log parser, metadata extractor, and event recognizer, a matching test file with a roundtrip test, and a sample log fixture, then runs pytest. A developer uses it when integrating a new firmware target.
- Scaffolds a new board/framework adapter for Firmware Replay Lab
- Generates a Python parser, metadata extractor, event recognizer, tests, and log fixtures
- Runs uv run pytest -q to verify the new adapter
Adapter Scaffold by the numbers
- 1 all-time installs (skills.sh)
- Ranked #240 of 290 Python skills by installs in the Skillselion catalog
- Data as of Jul 25, 2026 (Skillselion catalog sync)
adapter-scaffold capabilities & compatibility
- Capabilities
- code scaffolding · log parsing · test generation
- Use cases
- testing · api development
- Pricing
- Free
What adapter-scaffold says it does
You are scaffolding a new platform adapter for Firmware Replay Lab.
Keep adapters thin: parse and normalize, do not interpret.
Do not add platform-specific dependencies to the core package.
npx skills add https://github.com/agodianel/firmware-replay-lab --skill adapter-scaffoldAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | July 25, 2026 |
| Repository | agodianel/firmware-replay-lab ↗ |
What it does
Scaffold a Python adapter (parser, tests, fixtures) for a new firmware board or framework.
Who is it for?
generating a thin, tested log-parsing adapter for a new board or framework
Skip if: interpreting firmware logs or adding platform-specific dependencies to the core package
When should I use this skill?
adding ESP32/STM32 support or integrating a new firmware target
What you get
A new adapter module plus its tests and a sample log fixture are scaffolded and verified with pytest.
- adapter module in src/firmware_replay_lab/adapters
- test file
- sample log fixture
By the numbers
- 5-task scaffolding workflow
- roundtrip test: parse then bundle then evaluate
Files
You are scaffolding a new platform adapter for Firmware Replay Lab.
Inputs
- Platform name: $ARGUMENTS
Tasks
1. Create src/firmware_replay_lab/adapters/{platform}.py with:
- A log parser function that converts platform-specific serial output into
SerialLineentries. - A metadata extractor that identifies firmware version, target, and board from log headers or build info.
- An event recognizer for platform-specific structured events (e.g. ESP32 panic handler output, STM32 HardFault dumps).
2. Create tests/test_adapter_{platform}.py with:
- A test using a sample log snippet.
- A roundtrip test: parse → bundle → evaluate.
3. Add a sample log fixture in tests/fixtures/{platform}/. 4. Update the adapter registry if one exists. 5. Run uv run pytest -q to verify.
Rules
- Keep adapters thin: parse and normalize, do not interpret.
- Preserve all original log text; normalization adds structure, it does not discard data.
- Use the generic adapter interface pattern from existing adapters.
- Do not add platform-specific dependencies to the core package.
Related skills
FAQ
What does the generated adapter contain?
A log parser, a metadata extractor for firmware version/target/board, an event recognizer, a test file with a roundtrip test, and a sample log fixture.
How thin should adapters be?
Keep adapters thin: parse and normalize, do not interpret, and preserve all original log text.