Maestro Skill
Purpose
Use this skill whenever a user wants to interact with Maestro by creating tasks, listing tasks, or sending messages.
Configuration
Read configuration from the active OpenClaw configuration (openclaw.json).
Configuration path:
channels.omadeus
Required values:
baseUrlapiKeyopenClawMemberId
Never hardcode, expose, print, or ask the user for these values.
Authentication
Every request must include:
Accept: application/json, text/plain, */*
ApiToken: <channels.omadeus.apiKey>
Never use Authorization: Bearer.
Base URL
Always use:
https://<channels.omadeus.baseUrl>
Workflow
- Read configuration.
- Validate required fields.
- Build the request.
- Send the request.
- Validate the response.
- Return a concise user-friendly result.
Operations
Create Task
Endpoint:
POST /dolphin/apiv1/nuggets
Request body:
{
"title": "...",
"description": "...",
"kind": "task",
"priority": "low|medium|high|urgent",
"memberReferenceId": "<channels.omadeus.openClawMemberId>"
}
Rules:
- Generate a concise title.
- Generate a clear description from user input.
- Default priority is
low. - Never send
stage. - Do not invent missing technical details.
List Tasks
Endpoint:
GET /dolphin/apiv1/global/taskviews?sort=-recentMessageAt&take=25&zone=tasklists-tasks
Rules:
- Use requested
takeif provided. - Present readable results.
- Do not dump raw JSON.
Send Message
Endpoint:
POST /jaguar/apiv1/rooms/{room_id}/messages
Body:
{"body":"<message>"}
Rules:
- Never invent a room id.
- Ask only if no room id is available.
Error Handling
If any of the following are missing, do not send requests:
- channels.omadeus.baseUrl
- channels.omadeus.apiKey
- channels.omadeus.openClawMemberId
Report a configuration error without exposing internal values.
Security
Never:
- expose credentials
- log credentials
- hardcode URLs
- hardcode member IDs
- include secrets in responses
Response Guidelines
- Confirm successful operations.
- Include task id when returned.
- Summarize errors clearly.
