Betty Framework

1. Reads Registries: Loads skills.json, commands.json, and hooks.json
2. Filters Active Skills: Processes only skills with status: active and defined entrypoints
3. Validates Handlers: Checks if handler files exist on disk
4. Generates Commands: Converts skill entrypoints to plugin.yaml command format
5. Preserves Metadata: Maintains existing plugin metadata (author, license, etc.)
6. Writes plugin.yaml: Outputs formatted plugin configuration to repo root
7. Reports Issues: Warns about missing handlers or inconsistencies

Usage

Basic Usage

python skills/plugin.sync/plugin_sync.py

No arguments required - reads from standard registry locations.

Via Betty CLI

/plugin/sync

Expected Registry Structure

The skill expects these registry files:

betty/
├── registry/
│   ├── skills.json      # Registered skills
│   ├── commands.json    # Registered commands
│   └── hooks.json       # Registered hooks
└── plugin.yaml          # Generated output

Behavior

1. Registry Loading

Reads JSON files from:

• registry/skills.json
• registry/commands.json
• registry/hooks.json

If a registry file is missing, logs a warning and continues with available data.

2. Skill Processing

For each skill in skills.json:

• Checks status: Only processes skills with status: active
• Looks for entrypoints: Requires at least one entrypoint definition
• Validates handler: Checks if handler file exists at skills/{skill_name}/{handler}
• Converts format: Maps skill entrypoint to plugin command schema

3. Command Generation

Creates a command entry for each active skill entrypoint:

- name: skill/validate
  description: Validate a skill manifest
  handler:
    runtime: python
    script: skills/skill.define/skill_define.py
  parameters:
    - name: manifest_path
      type: string
      required: true
      description: Path to skill.yaml file
  permissions:
    - filesystem:read
    - filesystem:write

4. Handler Validation

For each handler reference:

• Constructs full path: skills/{skill_name}/{handler_filename}
• Checks file existence on disk
• Logs warning if handler file is missing

5. Plugin Generation

Preserves existing plugin.yaml metadata:

• Plugin name, version, description
• Author information
• License
• Requirements
• Permissions
• Config sections

Replaces the commands section with generated entries.

6. Output Writing

Writes plugin.yaml with:

• Auto-generated header comment
• Properly formatted YAML (2-space indent)
• Generation timestamp in metadata
• Skill and command counts

Outputs

Success Response

{
  "ok": true,
  "status": "success",
  "output_path": "/home/user/betty/plugin.yaml",
  "commands_generated": 18,
  "warnings": []
}

Response with Warnings

{
  "ok": true,
  "status": "success",
  "output_path": "/home/user/betty/plugin.yaml",
  "commands_generated": 18,
  "warnings": [
    "Handler not found for 'api.validate': skills/api.validate/api_validate_missing.py",
    "Skill 'test.broken' has entrypoint without handler"
  ]
}

Failure Response

{
  "ok": false,
  "status": "failed",
  "error": "Failed to parse JSON from registry/skills.json: Expecting value: line 1 column 1"
}

Generated plugin.yaml Structure

The skill generates a plugin.yaml like this:

# Betty Framework - Claude Code Plugin
# Auto-generated by plugin.sync skill
# DO NOT EDIT MANUALLY - Run plugin.sync to regenerate