stream-job

Stream GKE agent job logs in a tmux pane for live output.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill stream-job
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stream-job
Source: https://github.com/declanshanaghy/fenrir-ledger/tree/main/.claude/skills/stream-job
Command: npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill stream-job

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stream agent logs for a GKE job to observe live output and diagnose issues.

Core Features & Use Cases

  • Resolve input to a GKE agent job using a cascade of rules (issue, PR, session ID, or direct job name).
  • Stream logs in a tmux pane for real-time visibility, with support for a single job or all active jobs.
  • Provide status updates, handle completed pods by saving logs, and offer quick access to branding helpers.

Quick Start

Run /stream-job <identifier> to start streaming the corresponding GKE agent job.

Frequently Asked Questions about stream-job

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

FAQPage Schema
How do I stream GKE agent logs in real time?

You can stream GKE agent logs in real time by running the stream-job command with an issue number, PR, session ID, or job name to route output directly to a tmux pane for live diagnostics.

Can I stream logs for all active GKE jobs at once?

Yes, you can stream all active GKE jobs concurrently. The workflow resolves your input and delegates to agent-logs.mjs to display real-time tmux pane streaming for every matching active job.

What identifiers can I use to resolve a GKE job for log streaming?

To resolve a GKE job for log streaming, you can provide an issue number, pull request, session ID, or direct job name. The tool uses a defined cascade to match the correct job.

How does tmux pane streaming work for Kubernetes job diagnostics?

Tmux pane streaming for Kubernetes diagnostics works by delegating to agent-logs.mjs, which pipes the live agent output directly into a visible tmux pane, allowing you to observe job execution in real time.

Does the stream-job workflow save logs when a GKE pod completes?

Yes, when a GKE pod completes, the workflow handles log persistence by saving the logs. It also provides status updates throughout the job lifecycle to help with issue diagnosis.

Why do I need tmux to observe live agent output from a GKE cluster?

You need tmux because the streaming workflow delegates to agent-logs.mjs to render the live GKE agent output directly within a tmux pane, ensuring continuous real-time visibility during active jobs.