matimo: Skill for Claude Code

Add a new Matimo tool: $ARGUMENTS

If no name given, ask: which provider package, what is the tool name, and which API endpoint it wraps.

---

Step 1 — Read official API docs

Fetch the real documentation (WebSearch / WebFetch). Do not guess parameter schemas or response shapes. Understand:

• Endpoint URL and HTTP method
• Required vs optional parameters (types, enums, constraints)
• Authentication method and required env vars / OAuth scopes
• Response schema (fields, types)
• Error codes and rate limits

---

Step 2 — Create the YAML definition

Path: packages/<provider>/tools/<tool-name>/definition.yaml

Execution type rules:

• type: http — Use for any standard REST call. The HTTP executor injects auth, builds headers/body/query automatically. This is almost always the right choice.
• type: function — Only when you need multi-step calls, response transformation, or file I/O. Requires co-located .ts and .py executor files.
• type: command — Shell CLI tools only. Requires allowCommandTools: true in policy (blocked by default).

Auth type mapping:

Provider auth style	authentication.type	Header value example
Bot token (Slack, Notion)	api_key	Bearer {SLACK_BOT_TOKEN}
PAT / API key in header	bearer	token {GITHUB_TOKEN}
HTTP Basic	basic	use username_env + password_env
OAuth2 access token	oauth2	Bearer {PROVIDER_ACCESS_TOKEN}

Run pnpm validate-tools immediately. Fix every error before the next step.

---

Step 3 — Executor files (only for type: function)

Both files live in the same directory as definition.yaml.

TypeScript — packages/<provider>/tools/<tool-name>/<tool-name>.ts:

import type { ToolParams } from '../../../core/src/core/models';

export async function execute(params: ToolParams): Promise<Record<string, unknown>> {
  const { param1, param2 } = params as { param1: string; param2?: string };
  // implementation
  return { success: true };
}