kitaru-investigationlisted

Guide users from their own agent code or recorded traces through Kitaru setup, session import or recording, human review, an accepted behavior, a versioned cohort, and evaluator selection, then hand one bounded change to the replay-experiment skill. Use when a user wants to connect or inspect an existing agent, import real traces, investigate a known bad or surprising session, discover recurring failure modes, learn the evidence-led review flow, resume an investigation, create a cohort from reviewed evidence, or author an evaluator for an accepted behavior. When a first-time user has no agent or evidence and wants a fast demonstration with the public returns-agent template, use the `kitaru-guided-tour` skill instead.
zenml-io/kitaru-skills · ★ 4 · AI & Automation · score 70

Install: claude install-skill zenml-io/kitaru-skills

# Kitaru investigation Treat this skill as Kitaru's evidence-led front door for real agents and traces. Guide one continuous journey from the evidence the user has to a reviewed behavior and, when they want to test a change, the `kitaru-replay-experiment` skill. ## Core contract - Treat the human as the judge. Select, summarize, organize, and compile evidence; never turn an agent suggestion into a human label. - Preserve durable Kitaru state. Re-read existing objects before creating replacements, and carry exact agent, session, investigation, investigation-session, annotation, cohort-version, evaluator, and evaluator-version identifiers forward. - Separate observed behavior from desired behavior. A trace records what happened, not what should have happened or whether the external outcome was correct. - Distinguish agent behavior, external dependency behavior, product purpose, and independent outcome evidence. - Use open observations before proposing a taxonomy. Deterministic signals may select sessions; they do not judge them. - Explain remote writes and paid or live execution before running them. Ask for one proportional confirmation at the point of action. - Prefer native Kitaru MCP operations when available. CLI-only operation is supported; use the structured CLI for local files, built-in wait behavior, or an operation MCP does not expose. - Run every Kitaru CLI command and SDK script with `KITARU_ACTIVE_SKILL=kitaru-investigation` set so the ser