meta-tools-lifecycle

Meta-Tools Lifecycle: Complete Workflow

This skill teaches you how to take a new tool from idea to first call: validate the YAML, write it to disk, get a human to approve it, reload the registry, and use it. Every tool you create is untrusted — it starts as a draft and cannot run until a human approves it.

The Complete Tool Lifecycle

1. Understand requirements
   ↓
2. Validate the YAML            matimo_validate_tool
   ↓
3. Create it on disk            matimo_create_tool      → status: draft, approvalState: pending
   ↓
4. Reload the registry          matimo_reload_tools     → the draft is registered, not yet runnable
   ↓
5. Ask a human to approve it    matimo_approve_tool     → a human confirms; status: approved
   ↓
6. Reload again                 matimo_reload_tools     → the approved tool is runnable
   ↓
7. Call the tool                (every call still asks a human: requires_approval is true)

Check progress at any point with matimo_get_tool_status and matimo_list_user_tools.

Step 1: Understand Requirements

Before writing YAML, clarify:

• What it does: read-only (GET) or changes data (POST/PUT/DELETE)
• Which endpoint: a public HTTPS API the developer allows
• Inputs: the parameters it needs
• Output: what the caller should get back

Is it allowed? Untrusted tools must be type: http, must not target localhost, private networks or cloud metadata addresses, must not use a matimo_ name, and must stay within the developer's allowed domains, HTTP methods (GET and POST by default) and credentials.

Step 2: Validate the YAML

Write the complete YAML first

name: weather_lookup                     # snake_case, unique
version: "1.0.0"                         # a string
description: Get current weather for a city
parameters:
  city:
    type: string                         # string | number | boolean | array | object
    required: true
    description: City name (e.g., "New York")
execution:
  type: http
  method: GET
  url: "https://api.weatherapi.com/v1/current.json?q={city}"