What problem does it solve?
Building an OpenClacky extension involves many moving parts — the ext.yml manifest, WebUI panels, API backends, skills, and agents — and small mistakes like a wrong slot name or mismatched view path silently break everything. This Skill guides the full lifecycle: scaffolding a new extension, debugging verify errors, and optionally publishing to the marketplace.
Core Features & Use Cases
- Scaffold new extensions: Turn a plain-language idea into a working skeleton with
clacky ext new, then reshape the panel, handler, and manifest to the real feature.
- Debug and verify: Diagnose
clacky ext verify errors by code (loader.error, schema.unknown_field, ref.missing_panel, etc.) and fix the top failure modes like wrong mount signatures, invalid slot names, and route mismatches.
- Publish to the marketplace: Pack and upload a local extension with
clacky ext publish, manage versions with --force, and unpublish when needed.
- Use Case: A user says "my extension panel shows a red error box" — the Skill identifies the wrong
ui.mount render signature, fixes it to (container, ctx, runtime), re-runs verify, and confirms the panel loads after a page reload.
Quick Start
Ask the AI to create a new OpenClacky extension that adds a notes panel to the session sidebar with a backend route to save notes.
