From epieczko-betty
Validates and registers command manifest files (YAML) to integrate new slash commands into Betty.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-1 --plugin epieczko-bettyThis skill uses the workspace's default tool permissions.
Validates and registers command manifest files (YAML) to integrate new slash commands into Betty.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Validates and registers command manifest files (YAML) to integrate new slash commands into Betty.
The command.define skill acts as the "compiler" for Betty Commands. It ensures a command manifest meets all schema requirements and then updates the Command Registry (/registry/commands.json) with the new command.
This skill is part of Betty's Layer 1 (Commands) infrastructure, enabling developers to create user-facing slash commands that delegate to agents, workflows, or skills.
python skills/command.define/command_define.py <path_to_command.yaml>
| Argument | Type | Required | Description |
|---|---|---|---|
| manifest_path | string | Yes | Path to the command manifest YAML to validate and register |
Schema Validation – Checks that required fields (name, version, description, execution) are present and correctly formatted (e.g., name must start with /).
Parameter Verification – Verifies each parameter in the manifest has name, type, and description, and that the execution target (agent/skill/workflow) actually exists in the system.
Registry Update – On success, adds the command entry to /registry/commands.json with status active.
/, e.g., /api-design)0.1.0)The execution field must contain:
skill, agent, or workflow/registry/skills.json/registry/agents.json/workflows/{target}.yamlname (required): Parameter nametype (required): Parameter type (string, number, boolean, etc.)required (optional): Whether parameter is requireddescription (optional): Parameter descriptiondefault (optional): Default valuedraft or active, defaults to draft){
"ok": true,
"status": "registered",
"errors": [],
"path": "commands/hello.yaml",
"details": {
"valid": true,
"status": "registered",
"registry_updated": true,
"manifest": {
"name": "/hello",
"version": "0.1.0",
"description": "Prints Hello World",
"execution": {
"type": "skill",
"target": "test.hello"
}
}
}
}
{
"ok": false,
"status": "failed",
"errors": [
"Skill 'test.hello' not found in skill registry"
],
"path": "commands/hello.yaml",
"details": {
"valid": false,
"errors": [
"Skill 'test.hello' not found in skill registry"
],
"path": "commands/hello.yaml"
}
}
# commands/api-design.yaml
name: /api-design
version: 0.1.0
description: "Design a new API following enterprise guidelines"
parameters:
- name: service_name
type: string
required: true
description: "Name of the service/API"
- name: spec_type
type: string
required: false
default: openapi
description: "Type of API specification (openapi or asyncapi)"
execution:
type: agent
target: api.designer
status: active
tags: [api, design, enterprise]
$ python skills/command.define/command_define.py commands/api-design.yaml
{
"ok": true,
"status": "registered",
"errors": [],
"path": "commands/api-design.yaml",
"details": {
"valid": true,
"status": "registered",
"registry_updated": true
}
}
If the target agent doesn't exist:
$ python skills/command.define/command_define.py commands/hello.yaml
{
"ok": false,
"status": "failed",
"errors": [
"Agent 'api.designer' not found in agent registry"
],
"path": "commands/hello.yaml"
}
Commands can be validated as part of a workflow:
# workflows/register_command.yaml
steps:
- skill: command.define
args:
- "commands/my-command.yaml"
required: true
Validate commands automatically when they're edited:
# Create a hook that validates command manifests on save
python skills/hook.define/hook_define.py \
--event on_file_save \
--pattern "commands/**/*.yaml" \
--command "python skills/command.define/command_define.py" \
--blocking true
| Error | Cause | Solution |
|---|---|---|
| "Missing required fields: name" | Command manifest missing name field | Add name field with value starting with / |
| "Invalid name: Command name must start with /" | Name doesn't start with / | Update name to start with / (e.g., /api-design) |
| "Skill 'X' not found in skill registry" | Referenced skill doesn't exist | Register the skill first using skill.define or fix the target name |
| "Agent 'X' not found in agent registry" | Referenced agent doesn't exist | Register the agent first using agent.define or fix the target name |
| "Workflow file not found" | Referenced workflow file doesn't exist | Create the workflow file at /workflows/{target}.yaml |
| "execution.type is required" | Missing execution type | Add execution.type field with value skill, agent, or workflow |
/registry/commands.json – updated with new or modified command entry/registry/skills.json) – for validating skill targets/registry/agents.json) – for validating agent targets/workflows/*.yaml) – for validating workflow targetsActive – This skill is production-ready and actively used in Betty's command infrastructure.