peek

Inspect a backgrounded dev-team session by parsing its JSONL transcript for recent activity.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill peek-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peek
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/peek
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill peek-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When orchestrating multiple dev-team sessions from a CTO session, you lose visibility into what a backgrounded agent is actually doing. This Skill tails the named repo's Phase 2 session JSONL transcript and surfaces recent thinking blocks, tool calls, and outputs without leaving the CTO session. ## Core Features & Use Cases - Live session inspection: Resolves a repo from the fleet registry (exact name or suffix alias), locates its active JSONL transcript, and parses the last ~50 entries into readable thinking, tool_use, and tool_result lines. - Stale-session detection: Detects when a sub-agent (e.g. a review engine) overwrote the recorded session ID and falls back to the largest recently-modified transcript. - CTO summary: Produces a 5-line status report covering current task, last completed action, stuck signals, elapsed time, and a keep-watching/intervene recommendation. - Use Case: The CEO asks "what is acme-ui doing right now?" — run /peek acme-ui to get a real-time summary of that dev team's progress without switching sessions. ## Quick Start Ask the agent to peek at a registered repo's dev-team session, for example: peek at what the acme-ui dev team is working on right now.

Frequently Asked Questions about peek

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

FAQPage Schema
How do I check what a background Claude Code session is doing?

Run the peek skill with the repo name, for example /peek acme-ui. It tails that repo's session JSONL transcript and prints recent thinking blocks, tool calls, and results, then summarizes current activity in five lines.

How do I monitor multiple dev-team agent sessions from one place?

Register each repo in the CTO fleet registry (.cto/projects.yaml), then invoke peek with any registered repo name. The skill resolves the repo path, finds its live transcript, and reports status without leaving the orchestrating session.

Why does peek show a different session ID than the recorded one?

Sub-agent sessions such as review engines fire the SessionStart hook and overwrite current-session.id. Peek detects this by preferring the largest JSONL modified in the last two hours and notes the discrepancy in its output.

What happens if the repo name does not match the registry?

Peek first tries an exact name match, then a suffix alias match (e.g. "tuner" matching "acme-tuner"). If nothing matches or the alias is ambiguous, it exits with an error listing the problem.

Can peek work without a configured CTO home?

No. Peek requires a CTO home containing .cto/projects.yaml and fails with a diagnostic error if no valid anchor is found, listing rejected candidates so you can fix the anchoring rather than guessing.