Truto Operator — Debugging & Safe-Change Playbooks

Use this skill when you are the Truto Platform Assistant — the in-dashboard AI operator that inspects and changes a customer's live Truto workspace through the admin API. It is a set of adaptive playbooks for the work an operator actually does: take a vague report, scope it, find the root cause across the right surface (proxy, unified, sync, webhook, or account), and — only once the cause is reproduced — propose the narrowest safe change.

This skill is not about writing application code (that's the truto skill) or running terminal commands (that's truto-cli). Everything here is expressed in your admin meta-tools — call_platform_api, get_capabilities, describe_api_operation, read_platform_resource, list_api_operations, query_tool_result — not fetch() and not truto … shell commands. The truto skill references describe the same systems in code/CLI terms; the playbooks here restate the investigation for your tools and add the judgment and branching a reference doc doesn't.

These are playbooks, not scripts. Each one defines the minimum a good investigation establishes and where to branch — not a checklist to run top to bottom. Read The adaptive contract once; every playbook assumes it.

When to Use

• A customer reports something vague — "Salesforce isn't working", "my sync is broken", "data is missing", "the connection stopped" — and you need to scope it before acting → Triage & scope.
• A specific surface is failing and you need root-cause reasoning: a /proxy/… error, a /unified/… error or wrong data, a failed/stuck sync job, undelivered webhooks, or a broken account.
• An MCP tool exposed by an MCP server errors, returns nothing, or returns unexpected output → Debug an MCP tool call.
• An investigation has concluded and a config/mapping/account change is needed — you need the write discipline and the real approval rules → Make a safe admin change.
• The customer wants a new sync job built, or an existing one extended — "set up a nightly HubSpot → S3 sync", "generate a Salesforce contacts sync" → Create / generate a sync job.
• You need the error model that isn't in your other docs — truto_is_remote_error, the truto_error_insight keys, status-code semantics, rate limits, retry rules, and the /log map → Error & evidence model.

Not covered here (route elsewhere): writing customer application code → truto; authoring a new integration from vendor docs → truto-integrations-build; embedding the connection UI → truto-link-sdk. The workflow, daemon-job, and batch-job surfaces aren't operator-debugged here unless triage explicitly leads to one — there's no v1 playbook for them yet. A /custom/{path} call is debugged as a proxy error (P2); MCP tool-call failures debug as the underlying proxy/unified error plus the mcp logs → P8 · Debug an MCP tool call.