EmberBSD User Skills

Instructions for AI agents that assist EmberBSD users. Use real CLI/API tools to complete the requested task. Keep personal software changes in the user's selected Ports repository.

Version 0.4.1 provides ten small skills. Each task skill has a narrow trigger, short instructions, and its own required references. The two legacy entry points now select a task skill. The package uses Agent Plugins and Agent Skills.

Select a task skill

Skill	Use it when
`emberbsd-user-guide`	An EmberBSD user task needs skill selection
`emberbsd-manage-app`	You need to install, configure, update, or remove an application
`emberbsd-diagnose-device`	A device or application has a fault
`emberbsd-capture-network`	You need packet/HCI evidence or network measurements
`emberbsd-personal-ports`	You need a personal application patch across upstream updates
`emberbsd-github`	You need to create, synchronize, or publish the selected repository
`emberbsd-install`	An installation task needs target selection
`emberbsd-install-board`	You need EmberBSD on a board's card or onboard storage
`emberbsd-install-vm`	You need an aarch64 guest on a desktop VM host
`emberbsd-install-phone`	You need installation inspection or a first port track for a USB-connected phone or tablet

Load only the skills needed for the requested result. Each folder works alone with its bundled references, Codex metadata, and icon. Skills refer to other skills by name. Public source links provide instructions when another skill is unavailable. Legacy reference paths remain as short links to their new owners.

Keep the requested scope

Package	Intended tasks
EmberBSD-User-Skills (`emberbsd-user`)	Device operation, application configuration, personal patches, personal Ports publication, and supported installation
Ember-Agent-Skills (`emberbsd-development`)	Application development, OS changes, board development, shared ports, and requested contributions

Personal third-party patches and their builds remain user tasks. A personal patch does not require an upstream PR. Select the package by the requested result when both packages are installed. Reuse authorization for the exact action, target, and data loss. Keep credentials, private traces, and backups out of public reports.

For example, ask your assistant:

Use emberbsd-personal-ports to change this application's default behavior in my personal Ports repository. Test the change with the current upstream release. Use emberbsd-github to publish it to the repository I selected.

A completed build does not establish the requested behavior. The assistant must investigate failures and rerun the affected checks. Target execution remains untested when the selected device is unavailable.

Install the package or a skill

Use your client's documented installation mechanism.

For Agent Plugins, load the repository root and select emberbsd-user.
For Agent Skills, load each selected skills/<name>/ folder in full.
For manual use, read the selected SKILL.md and its required references.

Retain the repository's MIT license. Manual reading does not register automatic discovery. Keep your project's existing instructions.

See the Codex adapter for that client. ZCode and Claude Code use .claude-plugin/marketplace.json. In ZCode, add oxtech-ember/EmberBSD-User-Skills through Settings → Plugin Management → Discover → +. Install emberbsd-user from that catalog. In Claude Code, use these commands:

/plugin marketplace add oxtech-ember/EmberBSD-User-Skills
/plugin install emberbsd-user@emberbsd-user-skills

The portable format does not prescribe a universal installation command.

Tools and current limits

Skills contain instructions and packaging checks. They do not supply a package manager, device agent, GitHub client, credentials, or MCP server. SDK and Runtime currently provide design boundaries without released CLI/API interfaces. The assistant must recheck current sources before using future interfaces. Ports owns shared recipes and compatibility patches. Your personal Ports owns your chosen behavior changes.

A phone model without an OS installer is a first port, not a refusal. The phone skill runs read-only identity inspection and its first port track. The track collects identity, boot chain, and prior art, then proposes the bring-up plan. The OS development VM image declares its own input provenance. It remains separate from a general installation release. Board-specific procedures belong to the OS board catalog. EmberBSD-DevBoards provides hardware references for developers building their own devices. Its reader guide and catalog lead to board, carrier, SoC, interface, and bootloader records. Use these records to check hardware identity and configuration applicability during installation or hardware diagnosis. Current support, installation procedures, and executable checks remain with OS and Ports.

Validate the package

Run the local consistency check:

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

Add --codex for isolated native discovery and icon path checks. Version 0.3.1 passed those native checks with Codex CLI 0.159.2 on 2026-10-11. Version 0.4.0 passed the local consistency checks on 2026-10-11. See packaging and acceptance for version-specific evidence and task scenarios. Version 0.4.1 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.

Package checks do not execute device workflows or establish agent behavior. Desktop icon rendering and on-device acceptance require separate checks. See skill writing rules for the controlled English style.

License

MIT.