From nordic
Use when developing with the nRF Connect SDK (NCS) / Zephyr on a Nordic SoC or DK — setup, build, program, debug, migrate, or look up Nordic docs. Encodes Nordic's official prompting guidance for the Nordic MCP server.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nordic:using-nordic-mcpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Nordic MCP is a hosted HTTP MCP server (`https://aidev.nordicsemi.com/mcp`, OAuth via
Nordic MCP is a hosted HTTP MCP server (https://aidev.nordicsemi.com/mcp, OAuth via
myNordic) that gives AI assistants access to nRF Connect SDK (NCS) documentation,
setup, build, program, and debug workflows. This skill encodes Nordic's official
guidance for prompting it well.
Mentioning "Use Nordic MCP" is enough — the server exposes its own tools, prompts, and resources and routes the request. Do not micro-manage individual tool names unless you need a specific fact or resource.
Before acting, establish (ask the user if missing):
nrf5340dk/nrf5340/cpuapp) or DK name.If the board target is unknown, resolve it with Nordic sources before relying on it for build or programming.
Use nordicsemi_search_sources with full-sentence questions for facts that change
between SDK versions: board targets, Kconfig symbols, devicetree bindings, nrfutil
syntax, recommended tools / J-Link versions. Read these resources when relevant:
nrfutil-manual — verify exact nrfutil syntax before suggesting commands.embedded-code-guidance-ncs-zephyr — read before reviewing or writing Zephyr code.Prefer Nordic sources over general model knowledge for Zephyr APIs, Kconfig, and devicetree details.
PAUSE and ask for explicit confirmation before any action that affects hardware or project files:
Keep these in separate chats so context stays focused. Start a fresh chat if answers drift or unrelated tasks pile up.
| Avoid | Use instead |
|---|---|
| Vague task requests | Give NCS version, full board target/DK, project path, intended result |
| One chat mixing setup + development | Separate chats per phase |
| Flashing before checking connected devices | Identify the target device and confirm first |
| Writing Zephyr from general model knowledge | Verify APIs/Kconfig/devicetree via Nordic sources |
/nordic-setup-ncs, /nordic-build-debug, /nordic-search-docs, /nordic-migrate.
npx claudepluginhub wellwells/nordic-claude-plugin --plugin nordicGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.