Write or convert a structured (deterministic) procedure

Both procedure forms are first-class. Pick deliberately:

• free_form: markdown with optional frontmatter and prose steps. The model reads it and applies judgement. Right when steps are guidance or need discretion. This is the default and usually the correct answer.
• deterministic: JSON compiled into a real state machine. Steps run in order, exactly as written. Right when a tool sequence must be guaranteed (compliance, ticket hygiene, ordering that must not vary between runs).

Never convert one form to the other unless the user asked. Converting a working free-form procedure to deterministic trades away flexibility; say which capability is being traded, in one sentence, when you convert.

Everything is branch-scoped over the ConvAI REST API (host https://api.elevenlabs.io, header xi-api-key: $API_KEY). You need $AGENT_ID and $BRANCH_ID. Create and edit follow the draft then publish model (see the architect-manage-procedures skill): a create posts a draft, an edit patches the draft, and a PATCH /v1/convai/agents/$AGENT_ID?branch_id=$BRANCH_ID publishes pending drafts into a new version.

Do not guess the schema

There is no tool_code step type and no nested tool_code object. Use the schema below, or read an existing deterministic procedure's content as a template (list procedures via GET /v1/convai/agents/$AGENT_ID/branches/$BRANCH_ID/procedures, which returns type and full content for every procedure). Validate the JSON before publishing with POST /v1/convai/agents/$AGENT_ID/branches/$BRANCH_ID/procedures/compile.

Authoritative content schema

content is a JSON string with exactly two top-level keys. steps must be non-empty.