machina-agent

Diagnose MachinaMed agent errors in GKE environments from agent-trace.log.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/NumberOne-AI/machina-meta --skill machina-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: machina-agent
Source: https://github.com/NumberOne-AI/machina-meta/tree/main/.claude/skills/machina-agent
Command: npx skills add https://github.com/NumberOne-AI/machina-meta --skill machina-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators diagnose and trace errors in the MachinaMed medical agent ecosystem running on GKE, enabling faster identification and remediation of failures.

Core Features & Use Cases

  • Invocation tracing: Follow an incident from user message to agent routing and final response, including MALFORMED_FUNCTION_CALL incidents.
  • Log analysis: Inspect the agent-trace.log and related files to identify errors, timings, and root causes.
  • Error reporting: Generate comprehensive Agent Trace Errors Reports to document issues and guide fixes.

Quick Start

  • Locate the API pod in the tusdi-dev namespace and note its name.
  • Read the agent-trace.log from the pod and filter for MALFORMED_FUNCTION_CALL errors.
  • Compile a comprehensive error report (AGENT_TRACE_ERRORS_YYYYMMDD.md) summarizing findings and root causes.

Frequently Asked Questions about machina-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a MALFORMED_FUNCTION_CALL error in a GKE deployment?

To trace a MALFORMED_FUNCTION_CALL error in a GKE deployment, locate the API pod in the tusdi-dev namespace, read the agent-trace.log, and filter for the specific error to identify the root cause.

How do I analyze agent-trace.log files to diagnose MachinaMed agent failures?

You analyze agent-trace.log files to diagnose MachinaMed agent failures by inspecting the logs to identify errors, timings, and root causes, which enables faster identification and remediation of failures.

What is the best way to generate an error report for MachinaMed agent incidents?

The best way to generate an error report for MachinaMed agent incidents is to compile a comprehensive report (AGENT_TRACE_ERRORS_YYYYMMDD.md) summarizing findings and root causes from the agent-trace.log.

Can I trace MachinaMed agent invocations end-to-end from user message to final response?

Yes, you can trace MachinaMed agent invocations end-to-end by following an incident from the user message through agent routing to the final response, including MALFORMED_FUNCTION_CALL incidents.

Does debugging MachinaMed agent errors in GKE require locating a specific API pod?

Yes, debugging MachinaMed agent errors in GKE requires locating the specific API pod in the tusdi-dev namespace and noting its name to read and filter the agent-trace.log effectively.

Why do I need to filter agent-trace.log when reproducing failures in GKE?

You need to filter agent-trace.log when reproducing failures in GKE to isolate MALFORMED_FUNCTION_CALL errors and trace timings, which is a necessary step for producing a comprehensive incident analysis report.