Ember Agent Skills

Task-specific instructions for AI agents working on EmberBSD. The package uses Agent Plugins and Agent Skills. Version 0.4.5 contains eight independently installable skills.

Skill	Task
`emberbsd-repository-guide`	Select a repository and task skill when ownership is unclear
`emberbsd-develop-app`	Create or develop an application or public example using verified interfaces
`emberbsd-build-kernel`	Prepare GCC16 tools and cross-build a kernel without an application sysroot
`emberbsd-port-software`	Port or modernize shared software and verify behavior against independent evidence
`emberbsd-add-board`	Integrate board build and boot support with measured hardware evidence
`emberbsd-build-static-base`	Build and inspect a static base set
`emberbsd-contribute`	Submit an authorized shared change through the accepted channel
`emberbsd-maintain-skills`	Maintain AI instructions, task boundaries, and client metadata

Each entry has a narrow task description and its own references, client metadata, and icon. The old repository-guide name remains a short selector. Its previous reference paths remain as small migration notes. No skill requires sibling files. Descriptions and procedures use simplified English in the style of ASD-STE100. See the authoring rules for limits and verification boundaries.

Purpose and related projects

Use the repository map to locate the owning public source. OS builds and drivers belong to EmberBSD. Third-party recipes belong to Ports. Public demonstrations belong to Examples. SDK and Runtime currently contain design documents; verify implemented interfaces before calling them. This package contains no MCP server or device runtime.

EmberBSD-User-Skills handles operation, installation, diagnostics, personal application changes, and user GitHub work. Editing an existing program for personal use does not require a contribution PR. Independent applications keep their own conventions, language, license, and publication scope. Keep the application's existing instructions when you install skills.

Development checks cover Cppcheck, GCC and Clang static analysis, and Valgrind Memcheck. The guidance includes upstream-versus-patch comparisons for ports, justified suppressions, and explicit platform limits. Kernel contracts and hardware acceptance remain separate. Version and dependency migrations use a small pilot, explicit behavior contracts, independent comparisons, and negative controls for the tests and comparator.

Add your board

Start with emberbsd-add-board, the board catalog, and the OS board procedure. Supply the model, revision, SoC, firmware, serial console, and available hardware access. The workflow covers kernel, DTS/ACPI, drivers, output bundles, boot selection, and evidence. Keep build, VM, and physical checks separate. A shared SoC does not prove peripheral support. An authorized shared change includes the board page and a concise catalog row.

EmberBSD-DevBoards provides hardware references for developers building their own devices. It separates board, carrier, SoC, interface, and bootloader knowledge. Start with its reader guide and catalog, then check each profile's sources and applicability. Drivers, build procedures, and current support evidence remain in their implementation repositories.

Use in your development environment

Install the repository root with a client that supports Agent Plugins and skills. Select the emberbsd-development plugin. Follow that client's documented Git, directory, or archive installation method.

For standalone Agent Skills, install the complete skills/<name>/ directory. Keep its references, agents/, and assets together. Retain the MIT notice. For manual use, ask the agent to read the selected SKILL.md and required references. Manual reading does not register automatic discovery.

Verify that the client lists all eight task names. For example:

Use emberbsd-build-kernel to cross-build my AArch64 EmberBSD kernel with GCC16 on host and target.

Use emberbsd-develop-app to create a UART decoder in my application repository and test synthetic input.

Use the client's explicit selector when available. $skill-name is client syntax, not a requirement of the portable format. Refresh the installed copy through that client and verify its version after updates.

Install in Codex

The Codex guide explains marketplace commands and icon path bases.

codex plugin marketplace add oxtech-ember/Ember-Agent-Skills --ref main
codex plugin list --marketplace ember-agent-skills --available --json
codex plugin add emberbsd-development@ember-agent-skills

These commands use the selected Git ref. An unmerged candidate requires its topic ref or a local test marketplace; main does not include draft changes.

Install in ZCode and Claude Code

Both clients use .claude-plugin/marketplace.json. In ZCode, add oxtech-ember/Ember-Agent-Skills in Settings → Plugin Management → Discover and install emberbsd-development. In Claude Code:

/plugin marketplace add oxtech-ember/Ember-Agent-Skills
/plugin install emberbsd-development@ember-agent-skills

The catalog points to the repository root. The Claude plugin manifest exposes skills/. The root plugin.json remains the canonical portable manifest.

Package structure

plugin.json                       Portable manifest and OpenAI plugin metadata
.agents/plugins/marketplace.json  Codex catalog
.claude-plugin/                   ZCode and Claude Code adapters
assets/emberbsd-logo.png          Plugin icon
skills/<name>/SKILL.md            One task and its discovery condition
skills/<name>/references/         Only that task's bundled instructions
skills/<name>/agents/openai.yaml  Codex skill presentation
skills/<name>/assets/             Standalone skill icon
scripts/check-package.rb         Package, prose, link, and optional native checks
scripts/test-check-package.rb    Validation regressions
scripts/org-grep                 Search every organization repository and report coverage
scripts/org-grep-test            Offline regressions for org-grep
docs/skill-writing.md             Task boundaries and simplified English rules
docs/packaging.md                 Packaging and behavior scenarios
docs/codex.md                     Codex commands and evidence

The AI plugin marketplace distributes agent skills. A proposed EmberBSD Wasm application catalog is a separate SDK/Runtime contract.

Validate a checkout

Use Ruby with its standard library:

ruby scripts/test-check-package.rb
ruby scripts/check-package.rb
ruby scripts/check-package.rb --codex

The last command requires Codex. It uses temporary profiles and reads native plugin and skill icon paths without changing saved client settings. The checks enforce prose limits and skill-local links. They do not certify the full ASD-STE100 dictionary or prove assistant behavior, device support, or desktop rendering. Version 0.4.4 passed local consistency, all 21 validator regressions, native Codex discovery, and plugin/skill icon resolution with Codex CLI 0.159.2 on 2026-10-15. The port skill also passed standalone reference/metadata/icon checks and four CLI comparison cases. Five fresh-context instruction trials included the comparator fault check and correct host resource sizing; five controls and the original skill omitted those two requirements. These bounded trials do not establish general assistant reliability or downstream port acceptance.

Version 0.4.5 passed package checks, 21 validator regressions, isolated skill checks, and native Codex discovery on 2026-10-15. See the DevBoards routing checks for evidence and limits.

Review the manual scenarios after behavior changes.

License

MIT.