Agent skill

Peripherals From Datasheet

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

Peripheral driver methodology skill from MCU reference manuals.

MITAuto-check passedDevelopment

Install Peripherals From Datasheet

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill peripherals-from-datasheet -a claude-code

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

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills peripherals-from-datasheet --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/baremetal/peripherals-from-datasheet .claude/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .claude/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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/baremetal/peripherals-from-datasheet

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 peripherals-from-datasheet -a codex

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

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills peripherals-from-datasheet --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/baremetal/peripherals-from-datasheet .agents/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .agents/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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 peripherals-from-datasheet -a cursor

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

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills peripherals-from-datasheet --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/baremetal/peripherals-from-datasheet .cursor/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .cursor/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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/baremetal/peripherals-from-datasheet

--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 peripherals-from-datasheet -a gemini-cli

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

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills peripherals-from-datasheet --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/baremetal/peripherals-from-datasheet .gemini/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .gemini/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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 peripherals-from-datasheet

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 peripherals-from-datasheet -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/baremetal/peripherals-from-datasheet .github/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .github/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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 peripherals-from-datasheet -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 peripherals-from-datasheet --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/baremetal/peripherals-from-datasheet .opencode/skills/peripherals-from-datasheet && 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 "peripherals-from-datasheet" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/baremetal/peripherals-from-datasheet into .opencode/skills/peripherals-from-datasheet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peripherals-from-datasheet", 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: peripherals-from-datasheet
GitHub stars: 253
Token cost: ~1k tokens
SKILL.md length: 239 words
Files: 1
Skills in repo: 138
Repo updated: Jun 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Peripheral driver methodology skill from MCU reference manuals.

Works in 7 steps: Reference manual navigation → Extract register map → Init sequence checklist → …
Reading register maps
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

Peripherals From Datasheet is an agent skill from mohitmishra786/low-level-dev-skills. Peripheral driver methodology skill from MCU reference manuals. Use when reading register maps, timing diagrams, and writing drivers from vendor documentation. Activates on queries about reference manual, register map, peripheral init sequence, or datasheet-driven driver design.

Its SKILL.md is about 1k 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, covering Diagrams. 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

Reading register maps
Timing diagrams
Writing drivers from vendor documentation

Example prompts

“/peripherals-from-datasheet”

Workflow steps

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

Reference manual navigation
Extract register map
Init sequence checklist
Bit definition discipline
Timing and busy-wait
Good vs bad driver structure
Agent usage examples

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 c).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Peripherals From Datasheet loads about 1k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 239 words of instructions outside code blocks.

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

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). 239 words, ~1,041 tokens.

Download SKILL.mdSave it as .claude/skills/peripherals-from-datasheet/SKILL.md (or your agent's skills folder).

name: peripherals-from-datasheet
description: Peripheral driver methodology skill from MCU reference manuals. Use when reading register maps, timing diagrams, and writing drivers from vendor documentation. Activates on queries about reference manual, register map, peripheral init sequence, or datasheet-driven driver design.

Peripherals from Datasheet

Purpose

Guide agents through a repeatable methodology for writing peripheral drivers from MCU reference manuals: locating register maps, interpreting bit definitions, following init sequences, respecting timing constraints, and producing maintainable register-level code. Pair with skills/baremetal/datasheet-and-refmanual-reading for doc-navigation methodology (kept as separate skills).

When to Use

Starting a driver without vendor HAL
Porting a peripheral between MCU families
Verifying HAL behavior against the reference manual
Debugging a peripheral that "should work" per examples

Workflow

Typical RM structure
├── Memory map (peripheral base addresses)
├── Peripheral chapter (UART, SPI, GPIO, ...)
│   ├── Functional description
│   ├── Register map (table of offsets)
│   ├── Register bit definitions
│   └── Timing / electrical notes
└── Electrical characteristics (clock limits, setup/hold)

Start with the programming model section before copying register writes.

2. Extract register map

/* From RM — USART base 0x40004400 */
typedef struct {
    volatile uint32_t SR;   /* 0x00 status */
    volatile uint32_t DR;   /* 0x04 data */
    volatile uint32_t BRR;  /* 0x08 baud */
    volatile uint32_t CR1;  /* 0x0C control */
    /* ... */
} USART_TypeDef;

#define USART2 ((USART_TypeDef *)0x40004400UL)

Verify offset column matches struct layout (padding for reserved words).

3. Init sequence checklist

Peripheral bring-up order
├── 1. Enable bus clock (RCC/APB/AHB register)
├── 2. Reset peripheral (if RM requires)
├── 3. Configure pins (GPIO alternate function)
├── 4. Configure peripheral registers (mode, baud, etc.)
├── 5. Enable peripheral (UE, TE, RE bits)
├── 6. Enable NVIC IRQ (if interrupt-driven)
└── 7. Verify status flags before first transaction

Bad — enable UART before clock:

USART2->CR1 |= USART_CR1_UE;  /* USART clock still off — no effect */

4. Bit definition discipline

/* From RM: CR1 M[1:0], PCE, PS, TE, RE, UE */
#define USART_CR1_UE   (1U << 13)
#define USART_CR1_TE   (1U << 3)
#define USART_CR1_RE   (1U << 2)

Document RM section number in comment for audit trail.

5. Timing and busy-wait

/* RM: poll BUSY flag until reset complete */
while (RCC->CR & RCC_CR_PLLRDY == 0)
    ;

Respect startup times (oscillator settle, PLL lock) from electrical characteristics chapter.

6. Good vs bad driver structure

Good — layered, RM-referenced:

void usart2_init(uint32_t baud) {
    rcc_enable_usart2();
    gpio_config_usart2_pins();
    usart2_set_baud(baud);
    USART2->CR1 = USART_CR1_TE | USART_CR1_RE | USART_CR1_UE;
}

Bad — magic numbers, no clock enable:

*(uint32_t*)0x4000440C = 0x2000;  /* what peripheral? which bit? */

7. Agent usage examples

/peripherals-from-datasheet Walk me through USART init from STM32 RM
/peripherals-from-datasheet What sections of the ref manual matter for SPI timing?

Common Problems

Symptom	Cause	Fix
Peripheral dead	Clock not enabled	RCC/APB enable bit first
Wrong baud rate	PCLK assumption wrong	Recompute using actual clock tree
GPIO AF wrong	MUX value from wrong table	Cross-check pinout + AF table
IRQ stuck	Status flag clear sequence wrong	RM "clearing flags" subsection
Silent data corruption	Endian or width mismatch	Match register access size

skills/baremetal/datasheet-and-refmanual-reading — fast RM navigation
skills/baremetal/mmio-and-bit-manipulation — register access patterns
skills/baremetal/gpio-baremetal — pin mux before peripheral enable
skills/embedded/linker-scripts — memory map alignment

Files

Just SKILL.md in skills/baremetal/peripherals-from-datasheet of mohitmishra786/low-level-dev-skills.

Open the folder on GitHubat commit bdc5847

Compare with similar skills

Peripherals From Datasheet 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.

Peripherals From Datasheet compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Peripherals From Datasheet this skillmohitmishra786/low-level-dev-skills	253	—	~1k	Automated safety check: Pass	MIT	3 mo ago
Archify Diagramstt-a1i/archify	81k	—	~2.9k	Automated safety check: Pass	MIT	today
JSON Canvasheyitsnoah/claudesidian	2.6k	18 repos	~3.5k	Automated safety check: Pass	MIT	6 mo ago
Diagram Designcathrynlavery/diagram-design	47k	1 repos	~7.5k	Automated safety check: Pass	MIT	yesterday
Fireworks Tech Graphtisfeng/Easydict	15k	1 repos	~1.4k	Automated safety check: Pass	MIT	3 days ago
Excalidraw Diagramcoleam00/excalidraw-diagram-skill	5k	2 repos	~6.1k	Automated safety check: Pass	None	7 mo ago

Similar skills

Archify Diagrams
tt-a1i/archify
Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.
81k GitHub stars~2.9k tokensUpdated today
DevelopmentAuto-check passed
JSON Canvas
heyitsnoah/claudesidian
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.
2.6k GitHub starsUsed in 18 repos~3.5k tokens
DevelopmentAuto-check passed
Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
47k GitHub starsUsed in 1 repo~7.5k tokens
DevelopmentAuto-check passed
Fireworks Tech Graph
tisfeng/Easydict
Create precise SVG technical diagrams, export PNG or offline HTML, and animate supported semantic SVGs to GIF.
15k GitHub starsUsed in 1 repo~1.4k tokens
DevelopmentAuto-check passed
Excalidraw Diagram
coleam00/excalidraw-diagram-skill
Create Excalidraw diagram JSON files that make visual arguments.
5k GitHub starsUsed in 2 repos~6.1k tokens
DevelopmentAuto-check passed
Draw.io Diagram Studio
Agents365-ai/drawio-skill
Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.
10k GitHub stars~2.4k tokensUpdated 7 days ago
DevelopmentAuto-check: notes

Questions about Peripherals From Datasheet

What does Peripherals From Datasheet do?

Peripheral driver methodology skill from MCU reference manuals. Peripherals From Datasheet is an agent skill from mohitmishra786/low-level-dev-skills. Peripheral driver methodology skill from MCU reference manuals.

When should I use Peripherals From Datasheet?

Peripherals From Datasheet fits situations like: reading register maps; timing diagrams; writing drivers from vendor documentation.

How do I install Peripherals From Datasheet in Claude Code?

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

How do I install Peripherals From Datasheet in Codex?

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

Can I use Peripherals From Datasheet 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 peripherals-from-datasheet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/peripherals-from-datasheet, .gemini/skills/peripherals-from-datasheet, .github/skills/peripherals-from-datasheet and .opencode/skills/peripherals-from-datasheet in your project.

What does Peripherals From Datasheet need to run?

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

Does Peripherals From Datasheet access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Peripherals From Datasheet 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 Peripherals From Datasheet use?

Peripherals From Datasheet 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 Peripherals From Datasheet use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Peripherals From Datasheet?

Skills that share tags, products or a category with Peripherals From Datasheet: Archify Diagrams (tt-a1i/archify, 81k stars), JSON Canvas (heyitsnoah/claudesidian, 2.6k stars), Diagram Design (cathrynlavery/diagram-design, 47k stars) and Fireworks Tech Graph (tisfeng/Easydict, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Peripherals From Datasheet?

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 Peripherals From Datasheet

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

Peripherals from Datasheet

Purpose

When to Use

Workflow

1. Reference manual navigation

2. Extract register map

3. Init sequence checklist

4. Bit definition discipline

5. Timing and busy-wait

6. Good vs bad driver structure

7. Agent usage examples

Common Problems

Related Skills

Files

Compare with similar skills

Similar skills

More from mohitmishra786/low-level-dev-skills

Related

Questions about Peripherals From Datasheet