New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Embedded Project Governance

by crichars in crichars/embedded-project-governance

A lightweight, risk-scaled workflow for AI-assisted embedded firmware development.

MITAuto-check passedDevelopment

Install Embedded Project Governance

skills CLI
$ npx skills add crichars/embedded-project-governance --skill embedded-project-governance -a claude-code

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

GitHub CLI
$ gh skill install crichars/embedded-project-governance embedded-project-governance --agent claude-code

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

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

Facts

Skill name
embedded-project-governance
GitHub stars
104
Token cost
~1.1k tokens
SKILL.md length
462 words
Files
12 (incl. scripts)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

A lightweight, risk-scaled workflow for AI-assisted embedded firmware development.

  • Works in 8 steps: Read the project's AGENTS.md,… → Report confirmed facts, assumptions,… → Choose the lightest process that… → …
  • Onboarding an embedded project
  • SKILL.md covers Start With The Smallest Useful…, Initialize A Project When…, Workflow and Risk Gates
  • Runs PowerShell scripts from its folder

What it does

Embedded Project Governance is an agent skill from crichars/embedded-project-governance. A lightweight, risk-scaled workflow for AI-assisted embedded firmware development. Use when onboarding an embedded project, investigating or implementing firmware changes, working around generated code, handling shared interfaces, protocols, Flash/NVM, boot, DMA, ISR/RTOS concurrency, hardware bring-up, recovery, or target verification. Supports minimal user input and structured Issue-style tasks.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts (for example `README.md`, `agents/openai.yaml` and `project-template/.ai-governance/capability-map.md`).

It sits in Development, covering Embedded systems. The repository describes itself as: 面向 AI 辅助嵌入式固件开发的轻量、风险分级治理 skill. The licence is MIT.

When your agent uses it

  • Onboarding an embedded project
  • Implementing firmware changes
  • Working around generated code
  • Handling shared interfaces

Example prompts

  • “/embedded-project-governance”

Requirements

  • PowerShell

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the project's AGENTS.md, PROJECT.md, capability map when present,
  2. Report confirmed facts, assumptions, conflicts, unknowns, existing reusable
  3. Choose the lightest process that protects the task. Use the project's task,
  4. Propose the smallest change and observable acceptance conditions. Do not edit
  5. Implement only the approved scope, reusing existing drivers, BSP, SDK, HAL,
  6. Ask the maintainer to build, flash, and observe the target when required.
  7. Record actual evidence, skipped checks, open items, and residual risk. Do not
  8. Run a correctness review and a minimality review for unnecessary complexity.

What it can do on your machine

Read from SKILL.md and the folder at commit d4aac8d. 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

    Ships 1 file in scripts/ (PowerShell), which the agent can run.

    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

Embedded Project Governance loads about 1.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 462 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~1.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); the scripts in this folder are not scanned.

SKILL.md

The full file from crichars/embedded-project-governance at commit d4aac8d, republished under its MIT licence (© crichars). 462 words, ~1,063 tokens.

Download SKILL.mdSave it as .claude/skills/embedded-project-governance/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
embedded-project-governance
description
A lightweight, risk-scaled workflow for AI-assisted embedded firmware development. Use when onboarding an embedded project, investigating or implementing firmware changes, working around generated code, handling shared interfaces, protocols, Flash/NVM, boot, DMA, ISR/RTOS concurrency, hardware bring-up, recovery, or target verification. Supports minimal user input and structured Issue-style tasks.

Embedded Project Governance

Use this skill to keep embedded firmware changes minimal, authorized, and verifiable. It complements the project's AGENTS.md; it does not replace chip specifications, project facts, hardware judgment, IDE operation, flashing, or target-board testing.

Start With The Smallest Useful Input

Accept either:

text
Project path: <path>
Goal or observed problem: <one or two sentences>
Please investigate first; do not edit code yet.

or the structured form:

text
Goal: <observable result>
Scope: <files, modules, or boundaries>
Problem: <current symptom or reason>
Reference: <existing implementation or document>
Constraints: <must-not-change, resource, safety, or compatibility limits>
Acceptance: <how success will be observed>

Do not ask the user to provide facts that can be discovered from the repository or authoritative documents. Mark unresolved information as UNKNOWN and ask only questions that can change the design, risk, or acceptance result.

Treat fields in the current user request as the active task. Restate the parsed fields before investigation; an unfilled project template must not erase them. Do not ask again for a field the user already provided.

Initialize A Project When Requested

When the user explicitly asks to add the governance files to a project, run:

powershell
.\scripts\init-project.ps1 -ProjectPath <project-path>

Run the script from this skill's directory. By default it preserves existing files. Never use -Force unless the user explicitly approves overwriting the listed target files. Do not initialize a project merely because this skill was invoked; the workflow can inspect an existing project without copying files.

After initialization, read the created AGENTS.md, PROJECT.md, and capability map before proposing changes. Treat project-template/ as output material, not as additional skill instructions to load into every task.

Show full SKILL.md (248 more words)Show less

Workflow

  1. Read the project's AGENTS.md, PROJECT.md, capability map when present, active task, build files, and affected code.
  2. Report confirmed facts, assumptions, conflicts, unknowns, existing reusable capabilities, generated-code boundaries, and risk.
  3. Choose the lightest process that protects the task. Use the project's task, requirement, design, and verification templates only as needed.
  4. Propose the smallest change and observable acceptance conditions. Do not edit source, configuration, or build files until the approved scope is explicit.
  5. Implement only the approved scope, reusing existing drivers, BSP, SDK, HAL, RTOS, utilities, and supported generated-code extension points.
  6. Ask the maintainer to build, flash, and observe the target when required.
  7. Record actual evidence, skipped checks, open items, and residual risk. Do not call a build or a single successful transaction hardware acceptance.
  8. Run a correctness review and a minimality review for unnecessary complexity.

Risk Gates

Treat startup/reset, Flash/NVM/OTA, watchdog, DMA ownership, security, safety, power/actuator output, and irreversible operations as high risk. Before such an operation, confirm the target and range, bound the action, define timeout and recovery, and obtain explicit approval. After important failures, verify the system is retryable, safe, or explicitly terminal.

For Flash/NVM work, confirm the storage type and layout, target range, erase and write granularity and alignment, endurance, integrity or atomicity, power-loss recovery, ownership, and target verification method before implementation.

Use the project status ladder:

Planned -> Implemented -> Build Passed -> Host Verified -> HW Verified -> Accepted

Keep project-specific facts in project files and keep this workflow reusable.

© crichars, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts) in the repository root of crichars/embedded-project-governance.

  • SKILL.md
  • LICENSE
  • README.md
  • agents/openai.yaml
  • project-template/.ai-governance/capability-map.md
  • project-template/AGENTS.md
  • project-template/PROJECT.md
  • project-template/docs/templates/design.md
  • project-template/docs/templates/requirement.md
  • project-template/docs/templates/task.md
  • project-template/docs/templates/verification.md
  • scripts/init-project.ps1

Open the folder on GitHubat commit d4aac8d

Compare with similar skills

Embedded Project Governance 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.

Embedded Project Governance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Embedded Project Governance this skillcrichars/embedded-project-governance104—~1.1kAutomated safety check: PassMIT
Authoring VPhone Patch SetsLakr233/vphone-cli15k—~4.6kAutomated safety check: PassMIT
Sipeed I2C and SPI Hardware Controlsipeed/picoclaw30k—~578Automated safety check: PassMIT
RuView Hardware Setupruvnet/RuView97k—~1.8kAutomated safety check: NotesMIT
Esp32 Firmware Engineeralxv2016/folloup-sticky1171 repos~3.8kAutomated safety check: PassGPL-3.0
ExecuTorch Binary Size Reductionpytorch/executorch5.1k—~793Automated safety check: PassCustom licence

Similar skills

  • Authoring VPhone Patch Sets

    Lakr233/vphone-cli

    Explains how to declare a firmware patch in a vphone patch set, add a new set, or write a preset, including naming, gating and the checks that catch undeclared patches.

    15k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Sipeed I2C and SPI Hardware Control

    sipeed/picoclaw

    Reads and controls I2C and SPI peripherals on Sipeed boards such as LicheeRV Nano, MaixCAM and NanoKVM through the i2c and spi tools.

    30k GitHub stars~578 tokensUpdated today
    DevelopmentAuto-check passed

  • RuView Hardware Setup

    ruvnet/RuView

    Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.

    97k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check: notes

  • Esp32 Firmware Engineer

    alxv2016/folloup-sticky

    ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.

    117 GitHub starsUsed in 1 repo~3.8k tokens
    DevelopmentAuto-check passed

  • ExecuTorch Binary Size Reduction

    pytorch/executorch

    Measures and shrinks the ExecuTorch runtime binary by building a size test, analyzing it with bloaty and landing each reduction as its own pull request.

    5.1k GitHub stars~793 tokensUpdated today
    DevelopmentAuto-check passed

  • RuView mmWave Radar Setup

    ruvnet/RuView

    Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.

    97k GitHub stars~907 tokensUpdated today
    DevelopmentAuto-check: notes

Categories

Questions about Embedded Project Governance

What does Embedded Project Governance do?

A lightweight, risk-scaled workflow for AI-assisted embedded firmware development. Embedded Project Governance is an agent skill from crichars/embedded-project-governance. A lightweight, risk-scaled workflow for AI-assisted embedded firmware development.

When should I use Embedded Project Governance?

Embedded Project Governance fits situations like: onboarding an embedded project; implementing firmware changes; working around generated code; handling shared interfaces.

How do I install Embedded Project Governance in Claude Code?

Run `npx skills add crichars/embedded-project-governance --skill embedded-project-governance -a claude-code`. Or copy the skill folder (the crichars/embedded-project-governance repository) into .claude/skills/embedded-project-governance in your project. Claude Code loads it when a task matches its description.

How do I install Embedded Project Governance in Codex?

Run `npx skills add crichars/embedded-project-governance --skill embedded-project-governance -a codex`. Or copy the skill folder (the crichars/embedded-project-governance repository) into .agents/skills/embedded-project-governance in your project. Codex loads it when a task matches its description.

Can I use Embedded Project Governance 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 crichars/embedded-project-governance --skill embedded-project-governance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/embedded-project-governance, .gemini/skills/embedded-project-governance, .github/skills/embedded-project-governance and .opencode/skills/embedded-project-governance in your project.

What does Embedded Project Governance need to run?

Going by SKILL.md and its folder, Embedded Project Governance needs PowerShell for the scripts in its folder. Our summary lists: PowerShell.

Does Embedded Project Governance 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 Embedded Project Governance 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Embedded Project Governance use?

Embedded Project Governance is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Embedded Project Governance use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Embedded Project Governance?

Skills that share tags, products or a category with Embedded Project Governance: Authoring VPhone Patch Sets (Lakr233/vphone-cli, 15k stars), Sipeed I2C and SPI Hardware Control (sipeed/picoclaw, 30k stars), RuView Hardware Setup (ruvnet/RuView, 97k stars) and Esp32 Firmware Engineer (alxv2016/folloup-sticky, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Embedded Project Governance?

crichars (a GitHub user) maintains it in crichars/embedded-project-governance, which has 104 GitHub stars. The repository was last updated on September 3, 2026.

Source: crichars/embedded-project-governance on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.