Agent skill

Device Tree

by mohitmishra786 in mohitmishra786/low-level-dev-skills

Device tree skill for Linux hardware description. An agent skill from mohitmishra786/low-level-dev-skills.

MITAuto-check passedDevelopment

Install Device Tree

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kernel-dev/device-tree .claude/skills/device-tree && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .claude/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/kernel-dev/device-tree .agents/skills/device-tree && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .agents/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/kernel-dev/device-tree .cursor/skills/device-tree && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .cursor/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/mohitmishra786/low-level-dev-skills.git --path skills/kernel-dev/device-tree

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/kernel-dev/device-tree .gemini/skills/device-tree && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .gemini/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/kernel-dev/device-tree .github/skills/device-tree && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .github/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills device-tree --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/kernel-dev/device-tree .opencode/skills/device-tree && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "device-tree" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/device-tree into .opencode/skills/device-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "device-tree", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: device-tree
GitHub stars: 253
Token cost: ~857 tokens
SKILL.md length: 190 words
Files: 1
Skills in repo: 138
Repo updated: Jun 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Device tree skill for Linux hardware description. An agent skill from mohitmishra786/low-level-dev-skills.

Works in 7 steps: DTS structure → Key properties → Phandles → …
Writing DTS/DTSI
SKILL.md covers Purpose, When to Use, Workflow and Common Problems, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Device Tree is an agent skill from mohitmishra786/low-level-dev-skills. Device tree skill for Linux hardware description. Use when writing DTS/DTSI, bindings, overlays, phandles, or debugging OF platform probe failures. Activates on queries about device tree, DTS syntax, phandle, devicetree bindings, DT overlay, or OF graph.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Linux. The repository describes itself as: A curated suite of AI agent skills for systems and low-level programming with C/C++, Rust, and Zig toolchains, covering compilers, debuggers, profilers, build systems…. The licence is MIT.

When your agent uses it

Writing DTS/DTSI
Debugging OF platform probe failures

Example prompts

“/device-tree”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

DTS structure
Key properties
Phandles
Kernel parsing
Compile and inspect
Overlays (configfs)
Agent usage

What it can do on your machine

Read from SKILL.md and the folder at commit bdc5847. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are dts, bash and c).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- devicetree.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Device Tree loads about 857 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 190 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~67
When it runs · the whole SKILL.md, loaded when a task matches: ~857

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitmishra786/low-level-dev-skills at commit bdc5847, republished under its MIT licence (© mohitmishra786). 190 words, ~857 tokens.

Download SKILL.mdSave it as .claude/skills/device-tree/SKILL.md (or your agent's skills folder).

name: device-tree
description: Device tree skill for Linux hardware description. Use when writing DTS/DTSI, bindings, overlays, phandles, or debugging OF platform probe failures. Activates on queries about device tree, DTS syntax, phandle, devicetree bindings, DT overlay, or OF graph.

Device Tree (Devicetree)

Purpose

Guide agents through Linux device tree source (DTS): syntax, bindings, phandles, overlays, and how the kernel OF (Open Firmware) layer parses hardware description into platform_device instances.

When to Use

Platform driver not probing — DT mismatch
Adding a new board .dts or fragment overlay
Understanding compatible, reg, interrupts, clocks properties
Cross-checking hardware with skills/kernel-dev/platform-device-model

Workflow

1. DTS structure

dts

/dts-v1/;
#include "soc.dtsi"

/ {
    model = "My Board";
    compatible = "vendor,my-board", "vendor,soc-family";

    soc {
        uart0: serial@40011000 {
            compatible = "vendor,uart";
            reg = <0x40011000 0x400>;
            interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&clk_uart0>;
            status = "okay";
        };
    };
};

2. Key properties

Property	Meaning
`compatible`	Driver match string (most specific first)
`reg`	MMIO address + length ( `#address-cells`, `#size-cells` )
`interrupts`	IRQ specifier (interrupt parent defines cells)
`clocks` / `clock-names`	phandle to clock provider
`status`	`"disabled"` skips probe

3. Phandles

dts

clk_uart0: clock-uart {
    compatible = "vendor,clk";
    #clock-cells = <0>;
};

serial@... {
    clocks = <&clk_uart0>;  /* phandle reference */
};

4. Kernel parsing

OF core reads DTB at boot
├── of_platform_populate() creates platform_devices
└── driver `.of_match_table` matches `compatible`

static const struct of_device_id my_of_match[] = {
    { .compatible = "vendor,uart" },
    { }
};
MODULE_DEVICE_TABLE(of, my_of_match);

5. Compile and inspect

bash

dtc -I dts -O dtb -o board.dtb board.dts
dtc -I fs -O dts /proc/device-tree 2>/dev/null | less
ls /sys/firmware/devicetree/base/

Bindings live at devicetree.org — always cite binding name in commits.

6. Overlays (configfs)

bash

# Runtime overlay apply (when CONFIG_OF_OVERLAY)
mkdir -p /config/device-tree/overlays/my-overlay
cat my-overlay.dtbo > /config/device-tree/overlays/my-overlay/dtbo

7. Agent usage

/device-tree Write DTS fragment for I2C sensor on i2c1 with interrupt on GPIO5

Common Problems

Symptom	Cause	Fix
Driver not bound	`compatible` typo	Match driver's `of_match_table`
Wrong MMIO	`#address-cells` mismatch	Follow SoC `.dtsi`
IRQ not firing	Wrong interrupt parent/cells	Copy from working board DTS
Probe defer loop	Clock/regulator missing	`-EPROBE_DEFER` supplier in DT
Overlay fails	Symbol unresolved	`__fixups__` / label exports

skills/kernel-dev/platform-device-model — probe and sysfs
skills/kernel/device-drivers — devm_of_iomap
skills/baremetal/datasheet-and-refmanual-reading — HW to DT mapping
skills/embedded/zephyr — Zephyr devicetree (different tooling)
skills/kernel-dev/bus-drivers-i2c-spi — bus node children

Files

Just SKILL.md in skills/kernel-dev/device-tree of mohitmishra786/low-level-dev-skills.

Open the folder on GitHubat commit bdc5847

Compare with similar skills

Device Tree next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Device Tree compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Device Tree this skillmohitmishra786/low-level-dev-skills	253	—	~857	Automated safety check: Pass	MIT	3 mo ago
Update .NET OS Packagesdotnet/core	22k	—	~2.3k	Automated safety check: Pass	MIT	yesterday
Cut Releasejfernandez/bpftop	2.7k	—	~2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Native Feel Cross Platform Desktopyetone/native-feel-skill	1.9k	1 repos	~1.5k	Automated safety check: Pass	MIT	4 mo ago
PlotJuggler 4 Perf ProfilingPlotJuggler/PlotJuggler	6.2k	—	~1.6k	Automated safety check: Notes	MPL-2.0	7 days ago
ONNX Runtime Source Buildmicrosoft/onnxruntime	22k	—	~1.4k	Automated safety check: Pass	MIT	today

Similar skills

Update .NET OS Packages
dotnet/core
Official
Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.
22k GitHub stars~2.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
2.7k GitHub stars~2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Native Feel Cross Platform Desktop
yetone/native-feel-skill
A skill your agent uses when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a…
1.9k GitHub starsUsed in 1 repo~1.5k tokens
DevelopmentAuto-check passed
PlotJuggler 4 Perf Profiling
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
6.2k GitHub stars~1.6k tokensUpdated 7 days ago
DevelopmentAuto-check: notes
ONNX Runtime Source Build
microsoft/onnxruntime
Official
Builds ONNX Runtime from source with its build scripts, explaining the update, build and test phases, key flags and where the build output lands.
22k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
JS Cpp Protocol
notepadqq/notepadqq
Reference for the communication protocol between the JavaScript editor (CodeMirror or Monaco) and the C++/Qt UI layer via QWebChannel.
2.3k GitHub stars~3.2k tokensUpdated 3 days ago
DevelopmentAuto-check passed

Questions about Device Tree

What does Device Tree do?

Device tree skill for Linux hardware description. An agent skill from mohitmishra786/low-level-dev-skills. Device Tree is an agent skill from mohitmishra786/low-level-dev-skills. Device tree skill for Linux hardware description.

When should I use Device Tree?

Device Tree fits situations like: writing DTS/DTSI; debugging OF platform probe failures.

How do I install Device Tree in Claude Code?

Run `npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a claude-code`. Or copy the skill folder (skills/kernel-dev/device-tree in mohitmishra786/low-level-dev-skills) into .claude/skills/device-tree in your project. Claude Code loads it when a task matches its description.

How do I install Device Tree in Codex?

Run `npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a codex`. Or copy the skill folder (skills/kernel-dev/device-tree in mohitmishra786/low-level-dev-skills) into .agents/skills/device-tree in your project. Codex loads it when a task matches its description.

Can I use Device Tree in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitmishra786/low-level-dev-skills --skill device-tree -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/device-tree, .gemini/skills/device-tree, .github/skills/device-tree and .opencode/skills/device-tree in your project.

What does Device Tree need to run?

SKILL.md names no scripts, command-line tools or credentials: Device Tree is instructions for the agent only.

Does Device Tree access the network?

SKILL.md names 1 domain. As links in the text: devicetree.org. This is read from the text; nothing was executed.

Is Device Tree safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Device Tree use?

Device Tree is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Device Tree use?

About 857 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Device Tree?

Skills that share tags, products or a category with Device Tree: Update .NET OS Packages (dotnet/core, 22k stars), Cut Release (jfernandez/bpftop, 2.7k stars), Native Feel Cross Platform Desktop (yetone/native-feel-skill, 1.9k stars) and PlotJuggler 4 Perf Profiling (PlotJuggler/PlotJuggler, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Device Tree?

mohitmishra786 (a GitHub user) maintains it in mohitmishra786/low-level-dev-skills, which has 253 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on June 27, 2026.

Source: mohitmishra786/low-level-dev-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Device Tree

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Device Tree (Devicetree)

Purpose

When to Use

Workflow

1. DTS structure

2. Key properties

3. Phandles

4. Kernel parsing

5. Compile and inspect

6. Overlays (configfs)

7. Agent usage

Common Problems

Related Skills

Files

Compare with similar skills

Similar skills

More from mohitmishra786/low-level-dev-skills

Related

Questions about Device Tree