dxos-blueprints

Formalize runtime AI toolkits as blueprints in DXOS.

512|47|Updated Apr 7, 2021
One-click install
npx skills add https://github.com/dxos/dxos --skill dxos-blueprints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dxos-blueprints
Source: https://github.com/dxos/dxos/tree/main/.cursor/skills/blueprints
Command: npx skills add https://github.com/dxos/dxos --skill dxos-blueprints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide for creating and integrating Blueprints in DXOS. Use when adding blueprints to plugins, wiring operations as tools, structuring blueprint definitions, or testing with AssistantTestLayer.

Core Features & Use Cases

  • Blueprints define AI toolkits for a domain (e.g., markdown, kanban). They combine operation definitions for tool schemas with operation handlers for runtime execution.
  • Example workflows show how to register blueprints within capabilities and plugins to enable runtime tool invocation.

Quick Start

Create a Blueprint with a key, an operations set, and a make factory, then wire it into your plugin for runtime use.

Frequently Asked Questions about dxos-blueprints

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

FAQPage Schema
How do I define AI toolkits as blueprints in DXOS?

To define AI toolkits as blueprints in DXOS, you formalize them using a three-part structure: a key, an operations set for tool schemas, and a make factory for runtime execution handlers.

How do I wire blueprint operations into a DXOS plugin?

Wiring blueprint operations into a DXOS plugin involves registering the blueprint within capabilities and plugins to enable runtime tool invocation and execution for specific domains like markdown or kanban.

Can I test AI tool handlers using AssistantTestLayer in DXOS?

Yes, you can test AI tool handlers using AssistantTestLayer in DXOS to validate blueprint integration patterns and ensure your operation schemas and runtime handlers function correctly before deployment.

What is the required structure for a DXOS blueprint definition?

A DXOS blueprint definition requires a three-part structure: a key identifier, an operations set defining tool schemas, and a make factory that generates operation handlers for runtime execution.

Does my DXOS plugin need dependencies to register AI toolkits?

Registering AI toolkits in DXOS plugins requires no external dependencies; blueprints are self-contained definitions combining operation schemas and handlers that integrate directly into capabilities for runtime use.