# Truto CLI Investigator

> General Truto CLI investigation workflow for platform issues across accounts, integrations, environment integrations, docs, capabilities, logs, and proxy or unified API behavior. Use when the user asks to investigate a Truto issue and no narrower Truto skill clearly owns it.

- Skill: `yuvraj3335/truto-cli-investigator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuvraj3335/truto-cli-investigator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuvraj3335/truto-cli-investigator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: yuvraj3335 (https://skillmd.com/u/yuvraj3335)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/yuvraj3335/truto-cli-investigator

---


# Truto CLI Investigator

## Mission

Turn a vague Truto problem into an evidence-backed diagnosis. Prefer read-only CLI inspection, narrow reproductions, and clear layer classification.

## Intake Heuristics

Proceed with any of these: account ID, tenant ID, integration slug, environment integration ID, resource/method/path, time window, error message, or customer issue text. Ask one concise question only when no safe target can be resolved.

If the user gives relative time like "today" or "yesterday", convert it to an explicit ISO window in the profile's expected timezone when possible.

## Workflow

1. Confirm scope:
   ```bash
   truto whoami -p "$PROFILE" -o json --no-color
   ```
2. Resolve the account if possible:
   ```bash
   truto accounts get "$ACCOUNT_ID" -p "$PROFILE" -o json --no-color
   truto accounts list --tenant-id "$TENANT_ID" -p "$PROFILE" -o json --no-color
   ```
3. Discover supported behavior:
   ```bash
   truto accounts tools "$ACCOUNT_ID" -p "$PROFILE" -o json --no-color
   truto capabilities "$ACCOUNT_ID" --target account -p "$PROFILE" -o json --no-color
   ```
4. Trace config lineage:
   ```bash
   truto environment-integrations get "$ENV_INTEGRATION_ID" -p "$PROFILE" -o json --no-color
   truto environment-integrations show-override "$ENV_INTEGRATION_ID" -p "$PROFILE" -o json --no-color
   truto integrations get "$INTEGRATION_ID" -p "$PROFILE" -o json --no-color
   ```
5. Pull the narrowest useful logs:
   ```bash
   truto logs --log-type unified_proxy_api --integrated-account-id "$ACCOUNT_ID" --start "$START" --end "$END" --limit 100 -p "$PROFILE" -o json --no-color
   ```
6. Reproduce the smallest read-safe call:
   ```bash
   truto proxy "$RESOURCE" -m "$METHOD" -a "$ACCOUNT_ID" --query-json "$QUERY_JSON" -p "$PROFILE" -o json --no-color
   truto unified "$MODEL" "$UNIFIED_RESOURCE" -m "$METHOD" -a "$ACCOUNT_ID" --query-json "$QUERY_JSON" -p "$PROFILE" -o json --no-color
   ```

Use `-v` on the reproduction only after the non-verbose output confirms the failure or is too thin.

## Layer Classifier

Assign exactly one primary layer and optional secondary contributors:

- Account/auth: wrong account, expired token, missing scopes, provider permission, reconnect required.
- Environment override: environment-specific auth, pagination, rate-limit, webhook, or base URL override.
- Catalog config: base integration method path, verb, auth placement, pagination, response path, or error handling.
- Unified mapping: proxy is correct but unified output/filter/body/error behavior is wrong.
- Docs/capabilities: runtime method exists but tool exposure, schema, or description rows are missing/stale.
- Customer request: invalid ID, invalid filter/body, unsupported operation, provider plan limitation.
- Provider upstream: provider rejects or fails a valid request.
- Truto runtime: Truto 5xx, queue/durable-object/logging/platform behavior.

## Output

Give a compact investigation report: scope, target, evidence, primary layer, reasoning, reproduction command, and next action. If data is missing, say which command would close the gap.