piflow-inspect

Inspect Pi Flow runs and nodes with piflowctl diagnostic commands.

103|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/blueif16/PiFlow --skill piflow-inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: piflow-inspect
Source: https://github.com/blueif16/PiFlow/tree/main/.claude/skills/piflow-inspect
Command: npx skills add https://github.com/blueif16/PiFlow --skill piflow-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The piflow-inspect skill solves the problem of efficiently debugging and analyzing Pi Flow runs and nodes, providing insights into performance, costs, timing, context composition, and more, without manually parsing internal data.

Core Features & Use Cases

  • Performance Insights: Offers detailed metrics for performance and cost analysis.
  • Timing and Context Analysis: Delivers insights into the timing of operations and the composition of contexts.
  • Debugging: Facilitates quick debugging of runs and nodes using pre-defined commands.
  • Use Case: Suppose you're running a complex Pi Flow with multiple nodes and need to identify why a particular node is performing slowly or consuming too many tokens.

Quick Start

Load piflow-inspect and run the telemetry command for detailed performance information on a specific node.

Frequently Asked Questions about piflow-inspect

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

FAQPage Schema
How do I debug a slow Pi Flow node?

This skill helps debug a slow Pi Flow node by running telemetry commands through piflowctl, delivering detailed performance metrics and timing insights to pinpoint operational bottlenecks.

What is the best way to analyze Pi Flow workflow performance and costs?

The best way to analyze Pi Flow performance and costs is to run diagnostic commands that extract runtime metrics, giving you detailed insights into token consumption and node timing without manual parsing.

Do I need piflowctl installed to inspect Pi Flow runs?

Yes, you need piflowctl installed and a fully set up Pi Flow environment, because this skill relies on executing piflowctl commands to retrieve runtime diagnostics and context analysis.

How does telemetry handle context composition analysis for Pi Flow workflows?

Telemetry handles context composition analysis by running pre-defined piflowctl commands that extract runtime context data, allowing you to review the composition and timing of operations across nodes.

Why does my Pi Flow node consume too many tokens?

To find why your Pi Flow node consumes too many tokens, this skill runs diagnostics to provide cost analysis and performance data, revealing the specific node's token usage and operational breakdown.

Are there limitations when using scripts for Pi Flow diagnostics?

The primary limitation is complete dependency on the piflowctl environment; without Pi Flow set up and piflowctl installed, the diagnostic scripts cannot retrieve runtime telemetry or performance data.