gpd-export-logs

Extract and filter GPD session event streams and execution traces into JSONL, JSON, or Markdown files.

Updated May 1, 2026
One-click install
npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-export-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-export-logs
Source: https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry/tree/main/.agents/skills/gpd-export-logs
Command: npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-export-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of exporting GPD observability session logs and execution traces, allowing for easy review, sharing, debugging, and archival.

Core Features & Use Cases

  • Session Log Export: Extracts and filters session event streams from GPD/observability/sessions/.
  • Trace Log Export: Collects trace logs from GPD/traces/ with optional filters.
  • Output Formats: Generates files in JSONL, JSON, or Markdown format.
  • Use Case: Suppose you need to share your GPD project's observability data with a colleague for review. You can use this Skill to export the relevant logs and traces in the desired format.

Quick Start

Export all GPD observability logs in JSONL format to the default directory using the 'gpd-export-logs' command.

Frequently Asked Questions about gpd-export-logs

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

FAQPage Schema
How do I export GPD observability session logs and execution traces?

To export GPD observability session logs and execution traces, you can extract and filter event streams from the sessions and traces directories, then write them to a specified output directory using dedicated export scripts.

What output formats are supported when exporting GPD session logs?

Exporting GPD session logs supports JSONL, JSON, and Markdown output formats, allowing you to generate files in the structure that best suits your review, sharing, or debugging needs.

Do I need cargo to export execution traces from a GPD project?

Yes, you need cargo and GPD's Rust-based tools to validate your project and export execution traces, as the export process relies on these dependencies to extract and filter session event streams.

Can I filter execution traces when exporting observability logs?

Yes, you can apply optional filters to collect trace logs from the GPD traces directory, ensuring the exported observability data only includes the relevant execution traces for your debugging or review.

What is the best way to share GPD observability data with a colleague for review?

The best way to share GPD observability data is to export the relevant session logs and execution traces into JSON or Markdown format, generating portable files that a colleague can easily review.