yarli-introspect

Inspect running or completed yarli processes for health, progress, and stuck states.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rahulrajaram/rahulskills --skill yarli-introspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yarli-introspect
Source: https://github.com/rahulrajaram/rahulskills/tree/main/skills/yarli-introspect
Command: npx skills add https://github.com/rahulrajaram/rahulskills --skill yarli-introspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues with stalled or malfunctioning yarli runs by providing detailed insights into process health, progress, and potential bottlenecks.

Core Features & Use Cases

  • Process Monitoring: Checks running yarli and codex processes for health, CPU, and memory usage.
  • Run State Analysis: Parses continuation.json and tranches.toml to understand the current objective, task progress, and exit status.
  • Backend Output Review: Analyzes codex session logs for token usage, context compactions, and commands executed.
  • Worktree Inspection: Examines git status and git diff in worktree directories for recent activity.
  • Stuck Detection: Identifies runs that are stuck based on inactivity, excessive context compactions, or token burn rates.
  • Actionable Recommendations: Suggests steps like killing processes, adjusting configurations, or waiting for completion.

Quick Start

Use the yarli-introspect skill to check the status of the current yarli run.

Frequently Asked Questions about yarli-introspect

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

FAQPage Schema
How do I diagnose a stuck yarli process that seems to be hanging?

Stuck yarli runs are detected by analyzing process inactivity, excessive context compactions in codex session logs, and abnormal token burn rates. The introspection skill monitors these metrics alongside worktree git status to pinpoint exactly why your automation run has stalled.

How does process monitoring detect when a yarli run is stuck?

Stuck yarli runs are detected by analyzing process inactivity, excessive context compactions in codex session logs, and abnormal token burn rates. The introspection skill monitors these metrics alongside worktree git status to pinpoint exactly why your automation run has stalled.

How do I check the tranche progress and objective of a running yarli run?

When a yarli run stalls, the introspection skill provides actionable recommendations for intervention based on derived heuristics. It suggests specific steps such as killing unresponsive processes, adjusting configurations, or waiting for completion based on your specific metrics.

What steps should I take to fix a stalled yarli automation run?

When a yarli run stalls, the introspection skill provides actionable recommendations for intervention based on derived heuristics. It suggests specific steps such as killing unresponsive processes, adjusting configurations, or waiting for completion based on your specific metrics.

Can I inspect codex session logs to understand token usage and context compactions?

Yes, you can review codex session logs to analyze backend output, including token usage, context compactions, and executed commands. This log analysis helps identify whether excessive compactions or token burn rates are causing your yarli run to get stuck.

Do I need any special dependencies to monitor and introspect yarli processes?

No special dependencies are required to introspect yarli processes. The monitoring functionality operates via standalone scripts that directly analyze process health, parse configuration files like tranches.toml, and inspect git worktree directories without external libraries.