analyze

Investigate systems using seven specialized analysis modes.

3|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Pixley-Growth/cal-plugin --skill analyze-pixley-growth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/Pixley-Growth/cal-plugin/tree/main/skills/analyze
Command: npx skills add https://github.com/Pixley-Growth/cal-plugin --skill analyze-pixley-growth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The 'analyze' skill addresses the challenge of performing complex investigations and analysis within a system or domain.

Core Features & Use Cases

  • 7 Analysis Modes: Offers a comprehensive suite of modes for different investigation scenarios, including 'inside-out', 'cake-walk', 'rubberneck', 'burst', 'bisect', 'trace', and 'diff-audit'.
  • Dynamic Pipeline Management: Automates the investigation process by selecting the best mode based on user input or by suggesting the most relevant mode.
  • Analysis Journaling: Provides a structured way to document the investigation process and findings.

Quick Start

Use the /cal:analyze command followed by the analysis mode and subject, such as '/cal:analyze inside-out the authentication system'.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I perform a deep system investigation across different debugging scenarios?

Deep system investigation is facilitated by providing seven specialized analysis modes tailored for different scenarios, such as comprehensive understanding, layering issues, focused scans, and binary searches. You select the appropriate mode and define the subject to begin the analysis.

What is the best way to trace issues end-to-end during system analysis?

The best way to trace issues end-to-end is using a dedicated trace mode. This mode specifically follows the flow of execution or data across system boundaries to identify where a breakdown occurs within the investigation pipeline.

Can I compare system states to find what changed during a debugging session?

Yes, you can compare system states using the diff-audit mode. This analysis mode specifically compares temporal states or configurations to pinpoint discrepancies, helping isolate what changed between different points in the system.

How do I narrow down a large system issue using binary search techniques?

You can narrow down large system issues using the bisect analysis mode. This mode applies binary search techniques to your investigation, systematically eliminating halves of the system to quickly isolate the root cause.

Do I need to manually select an analysis mode for every investigation?

No, manual mode selection is not strictly required. The dynamic pipeline management can suggest the most relevant analysis mode based on your initial input, or you can explicitly declare the mode and subject to direct the investigation.

How are findings documented during a complex system analysis?

Findings are documented using analysis journaling, which provides a structured way to record the investigation process. This ensures that the progression of the debugging steps and the resulting findings are captured systematically.