Limited Release. The EDK is currently in limited release and is not available to all customers. Commands, generated file layouts, and package APIs may change before general availability. Confirm you’re on the latest EDK version before starting new projects.
SKILL.md file and, when needed, supporting references or templates. A compatible coding assistant loads the relevant playbook to follow current EDK workflows and safety rules.
Understand the terminology
These three concepts are different:
- A coding-agent playbook guides a coding assistant. Manage it with
elementum playbooks.
- A platform agentic skill is an app-owned Elementum component authored with
defineSkill. Manage platform operations through the elementum skills command family.
- An A2A skill is a capability descriptor on an agent’s A2A card so other agents can discover that capability.
Coding-agent playbooks do not run inside an Elementum agent.
Available playbooks
/elementum handles general EDK workspace setup, authoring, pull, build, plan, and apply work./elementum-uat tests a deployed solution from records and automations through agents, tools, and complete business outcomes./elementum-debug diagnoses workspace, build, deployment, automation, tool, and agent failures from evidence./elementum-deployments configures and verifies platform cross-environment promotion when a deployment URL or asyncTaskId is provided./elementum-design designs and verifies record layouts, list views, information hierarchy, responsive behavior, and accessibility.
List bundled playbooks
Show every bundled playbook, its description, and installation status:
Use elementum playbooks list --json when another tool needs a machine-readable catalog.
Install or update playbooks
Install all bundled playbooks in the current project:
By default, files are installed under ./.agents/skills. Common alternatives are:
Without --yes, the command reports the destination and prints the command to confirm. Re-running installation replaces the selected installed copies with the versions bundled in the current toolchain.
Check status
Compare installed versions with the bundled versions:
The result identifies playbooks that are current, stale, missing, unstamped, or newer than the bundled copy. Update the toolchain before replacing a playbook that is newer than its bundled version.
Inspect paths and files
Print the source path for a playbook, or its embedded identifier when the source is bundled in the standalone CLI:
List every file bundled with one playbook:
Print the default SKILL.md or a named supporting file:
Use these inspection commands when your coding assistant cannot discover a playbook automatically or when you want to review its instructions before use.
Keep playbooks current
The CLI can warn during pull, plan, or apply when the core /elementum playbook is missing or stale. After updating the toolchain, refresh the installed copies:
Continue with Authoring for source conventions or Plan and Apply for reviewing and applying EDK changes.
