fixture-log

Fetch GKE agent logs and convert them into JSONL fixtures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines retrieving agent log files from GKE and converts them into fixtures for UI development and testing, reducing manual log collection time.

Core Features & Use Cases

  • Retrieve agent logs from fenrir-agents namespace in GKE.
  • Save as JSONL fixtures for monitor UI.
  • Supports session-based or bulk log extraction for multiple agents.

Quick Start

Run the fixture-log skill with a session-id to fetch the corresponding agent logs and save them as fixtures.

Frequently Asked Questions about fixture-log

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

FAQPage Schema
How do I fetch agent logs from GKE for monitor UI testing?

Fetch agent logs from GKE by extracting them from the fenrir-agents namespace and converting them into JSONL fixtures for monitor UI development. This skill streamlines log collection, reducing manual effort.

Can I extract logs for a specific session-id from the fenrir-agents namespace?

Yes, you can extract logs for a specific session-id from the fenrir-agents namespace. The skill supports single-session extraction via a session-id argument, guiding usage to ensure deterministic fixture output.

What is the best way to bulk extract agent logs from a GKE namespace?

Bulk extract agent logs from a GKE namespace by using the --all flag. This retrieves multiple agent logs simultaneously from the fenrir-agents namespace and saves them as JSONL fixtures for monitor UI development.

Does this log extraction tool require kubectl to fetch GKE logs?

The log extraction tool uses kubectl as an allowed tool to fetch GKE logs. The frontmatter defines allowed-tools and argument-hints, guiding usage and ensuring deterministic JSONL fixture output for the monitor UI.

Why convert agent logs into JSONL fixtures for UI development?

Convert agent logs into JSONL fixtures to provide deterministic test data for the monitor UI. This format standardizes log structure, streamlining UI development and testing by reducing manual log collection time.