chsh-sk-memfault

Orchestrates Memfault symbol uploads, OTA releases, and deployments for Nordic Wi-Fi firmware.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-memfault-chshzh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chsh-sk-memfault
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-memfault
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-memfault-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Memfault operations for the nordic-wifi-memfault firmware—uploading ELF symbols, creating OTA releases, deploying to cohorts, and decoding crash traces—involves error-prone manual steps across CLI tools, MCP queries, and multi-board builds, where mistakes like wrong workspace paths or version mismatches cause real incidents. ## Core Features & Use Cases - Workflow Dispatching: Routes requests to Workflow A (symbol upload for crash debugging), Workflow B (full release with symbols, OTA, and deployment), or Workflow C (abort/disable deployments) via the chsh-ag-memfault subagent. - Build and Flash Orchestration: Rebuilds firmware for nrf54lm20dk and nrf7002dk in parallel with correct version strings, and flashes boards without erasing Wi-Fi credentials stored in NVS. - Release Artifact Handling: Downloads CI-built ELF and signed binary artifacts from GitHub releases for re-deployment without rebuilding. - Use Case: After a crash report, invoke the skill to upload symbols for the current build, then decode the crash trace directly using Memfault MCP tools like trace_get. ## Quick Start Ask the agent to use the chsh-sk-memfault skill to upload symbols and deploy release v3.4.0.1 for the nordic-wifi-memfault project.

Frequently Asked Questions about chsh-sk-memfault

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload ELF symbols to Memfault for crash debugging?▼

Invoke the skill with a symbol upload or crash debug request, which triggers Workflow A through the chsh-ag-memfault subagent. After symbols are uploaded, use the mcp_memfault_trace_get tool with include_logs to decode crash traces directly.

How do I deploy an OTA update to a Memfault cohort?▼

Request a release or deploy action, which runs Workflow B: uploading symbols, creating the OTA release, and deploying to the cohort. You can rebuild locally or download CI-built artifacts from the GitHub release for the target version.

Why does my device report the wrong software version after OTA?▼

The embedded version string must match the Memfault software version, including the v prefix. Set CONFIG_MEMFAULT_NCS_FW_VERSION="v<tag>" in overlay-app-memfault-project-info.conf before building so the binary matches the release.

Why are my Memfault log files not appearing in the platform?▼

Memfault rate-limits log ingestion to roughly once per hour per device, silently dropping files while returning HTTP 202. Enable Server-Side Developer Mode on the device page to bypass limits during testing, and avoid 60-second upload intervals in production.

Can I flash nRF boards without losing Wi-Fi credentials?▼

Yes, use plain west flash without --recover or --erase flags, which wipe the NVS partition storing Wi-Fi credentials. The skill flashes by board serial number using nrfutil with the NCS toolchain.

What are the limitations of Memfault MCP tools versus the CLI?▼

Memfault MCP tools are read-only: they query devices, issues, traces, and metrics but cannot upload symbols, create releases, or deploy OTA. Those write operations require the CLI path handled by the chsh-ag-memfault subagent.