tlamatini-planner-trace-replay

Replay the latest build_global_execution_plan trace from tlamatini.log and summarize per-capability scores, keywords, and top-tool selections.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-planner-trace-replay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlamatini-planner-trace-replay
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/tlamatini_planner_trace_replay
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-planner-trace-replay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand why the global planner scored each capability by replaying the most recent trace from tlamatini.log and explaining the scoring rationale.

Core Features & Use Cases

  • Replay the tail of tlamatini/tlamatini.log to locate the most recent build_global_execution_plan call and its per-capability scores.
  • Summarize, for each capability, the assigned score, contributing keywords, and whether it was selected among the top tools.
  • Provide a concise rationale that helps engineers diagnose planning decisions and identify potential gaps.

Quick Start

Replay the latest planner trace and explain why each capability received its score.

Frequently Asked Questions about tlamatini-planner-trace-replay

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

FAQPage Schema
How do I explain planner trace scores from tlamatini.log?

You can replay the most recent build_global_execution_plan trace from tlamatini.log to summarize per-capability scores, contributing keywords, and whether each capability was selected among the top tools, alongside a concise scoring rationale.

Why does the global planner select certain capabilities over others?

The global planner selects capabilities based on assigned scores and contributing keywords. Replaying the trace reveals the exact per-capability scoring output, showing which tools were chosen among the top entries and explaining any deviations in the selection logic.

How do I debug planning decisions in Tlamatini?

Debugging planning decisions in Tlamatini involves replaying the latest build_global_execution_plan trace to diagnose why each capability received its score. This process highlights the contributing keywords and identifies potential gaps in the scoring rationale.

What is a build_global_execution_plan trace and when do I need it?

A build_global_execution_plan trace records the per-capability scoring output during global planning. You need it when diagnosing planning decisions, understanding why specific capabilities were scored or selected, and identifying potential gaps in tool selection logic.

Can I extract per-capability scores from a specific Tlamatini log file?

Yes, you can extract per-capability scores by locating the most recent build_global_execution_plan call in tlamatini.log. The process summarizes each capability's score, contributing keywords, and top tool selection status into a structured result.

What are the limitations of replaying the latest planner trace?

Replaying the latest planner trace is limited to analyzing only the most recent build_global_execution_plan entry in tlamatini.log, meaning it does not evaluate historical traces or provide real-time scoring adjustments for ongoing planning processes.