What problem does it solve?
Developers building on DXOS need a consistent way to expose domain capabilities (like markdown or kanban editing) as AI-callable tools, but wiring operation definitions, runtime handlers, and plugin capabilities together is error-prone without a clear pattern.
Core Features & Use Cases
- Skill Definition Pattern: Shows how to structure a skill with a unique key, an OperationHandlerSet for runtime execution, and a make factory producing Skill instances with tool schemas and instructions.
- Plugin Integration: Explains how to register skills via AppCapabilities.SkillDefinition capability modules and AppPlugin.addSkillDefinitionModule so Composer can discover them.
- Testing Support: Demonstrates using AssistantTestLayer from @dxos/assistant/testing to test operations and AI flows, invoking operations with Operation.invoke instead of the deprecated FunctionInvocationService.
- Use Case: You are adding a new markdown skill to a DXOS plugin and need to define Create/Open/Update operations, register the skill capability, and write tests that invoke those operations against ECHO types.
Quick Start
Ask the assistant to scaffold a new DXOS skill for your plugin with operation definitions, handlers, capability registration, and an AssistantTestLayer test.