Command Define

Validate command manifests and register slash commands in Betty.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/epieczko/betty --skill command-define
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Command Define
Source: https://github.com/epieczko/betty/tree/main/skills/command.define
Command: npx skills add https://github.com/epieczko/betty --skill command-define

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires registry.update, and includes scripts (resource) components.

What problem does it solve?

Integrating new custom commands into an AI assistant or framework requires a structured way to define their behavior, parameters, and execution logic. This Skill provides a robust validation and registration mechanism for new slash commands, streamlining their integration.

Core Features & Use Cases

  • Schema Validation: Checks that command manifests (.yaml files) adhere to the required structure and fields, ensuring consistency and preventing errors.
  • Execution Verification: Validates that the command's target (skill, agent, or workflow) actually exists in the system, preventing broken command invocations.
  • Registry Update: Automatically adds the validated command to the central Command Registry, making it discoverable and available for use.
  • Use Case: A developer wants to create a new /deploy command that triggers a specific workflow. They define the command in a YAML manifest, then use command.define to validate and register it, making /deploy available for immediate use by other users or agents.

Quick Start

Validate and register a new command manifest

python skills/command.define/command_define.py commands/my-deploy-command.yaml

Frequently Asked Questions about Command Define

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate and register a new slash command in Betty?

Command Define validates command manifests to register new slash commands. Define a YAML manifest with name (starting with '/'), version, description, and execution type, then run the validation to check target existence and update the command registry automatically.

What fields are required in a command manifest?

Command manifests must include name (starting with '/'), version, description, and execution details. The execution type must be skill, agent, or workflow, and the target must exist in the registry or workflow system for validation to succeed.

Can I use Command Define to verify that my command's target actually exists?

Yes, Command Define verifies execution target availability by checking skill, agent, and workflow registries before registration. This prevents broken command invocations by ensuring the target exists in the system.

What happens when I register a command with Command Define?

Command Define performs schema validation, verifies target existence, and automatically updates /registry/commands.json with an atomic operation. The validated command becomes immediately discoverable and available for use.

What validation errors should I watch for when defining commands?

Command Define enforces required fields, validates data types, ensures execution.type is skill, agent, or workflow, and confirms target existence. Missing fields, incorrect types, or nonexistent targets will block registration.