Devicetree logo

Devicetree

Community
beriberikix
devicetree

Devicetree management for Zephyr RTOS. Covers syntax, bindings, overlays, Hardware Model v2 (HWMv2), and advanced node/property deletion patterns. Trigger when defining hardware topology, creating overlays, or mapping pins and peripherals.

Overview

Publisherberiberikix
Repositoryzephyr-agent-skills
Skill namedevicetree
Stars
73
Forks
19
Bundled files
6
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by beriberikix on GitHub. Read the source before you install it.

Installation

Install the Devicetree AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/beriberikix/zephyr-agent-skills/tree/main/skills/devicetree
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/beriberikix/zephyr-agent-skills.git /tmp/zephyr-agent-skills
mkdir -p .claude/skills
cp -r /tmp/zephyr-agent-skills/skills/devicetree .claude/skills/devicetree
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Devicetree in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Devicetree on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Devicetree is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Zephyr Devicetree

The Devicetree (DT) is the source of truth for your hardware topology in Zephyr.

Core Workflows

1. Understanding Syntax & Nodes

Nodes, properties, and phandles form the hierarchy.

  • Reference: dt_syntax.md
  • Key Tools: Labels (&label), Properties (reg, status, compatible).

2. Working with Bindings

Mapping hardware descriptions to driver schemas.

  • Reference: dt_bindings.md
  • Key Tools: YAML bindings, compatible strings, pinctrl.

3. Application Overlays & HWMv2

Modifying board behavior for specific application needs.

  • Reference: dt_overlays.md
  • Key Tools: .overlay files, zephyr,chosen, variant-specific overlays.

4. Advanced Hardware Modification

Deleting and redefining nodes/properties for product variants.

  • Reference: dt_overlays.md
  • Key Tools: /delete-node/, /delete-property/.

Quick Start (Overlay)

dts
/* app.overlay */
&i2c1 {
  status = "okay";
};

&uart0 {
  status = "disabled";
};

Tooling & Validation

  • west build -t rom_report: See how devicetree definitions impact memory.
  • build/zephyr/zephyr.dts: Inspect the FINAL resolved devicetree after all overlays are applied.
  • build/zephyr/include/generated/zephyr/devicetree_generated.h: Inspect generated DT macros consumed by C code.

Automation Tools

Examples & Templates

Validation Checklist

  • Overlay compiles with no DTS syntax errors during west build.
  • Expected node status/properties are present in build/zephyr/zephyr.dts.
  • Expected DT macros exist in build/zephyr/include/generated/zephyr/devicetree_generated.h.
  • Application runs with peripherals enabled/disabled exactly as described by the overlay.

Resources

  • References:
    • dt_syntax.md: Core syntax and properties.
    • dt_bindings.md: Binding definitions and compatible mapping.
    • dt_overlays.md: Overlays, HWMv2, and deletion patterns.
  • Scripts:
    • overlay_include_check.py: Overlay sanity checker.
  • Assets:
    • app_overlay_template.overlay: Baseline overlay template.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Devicetree AI skill do?

Devicetree management for Zephyr RTOS. Covers syntax, bindings, overlays, Hardware Model v2 (HWMv2), and advanced node/property deletion patterns. Trigger when defining hardware topology, creating overlays, or mapping pins and peripherals.

Why use Devicetree on TypingMind?

Because you install it once and use it with any model. Devicetree is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Devicetree in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/beriberikix/zephyr-agent-skills/tree/main/skills/devicetree. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Devicetree?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Devicetree?

As many as you like. As long as a model supports skills, you can use Devicetree with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Devicetree AI skill free?

Yes. It is published on GitHub by beriberikix under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇