zakura-trace-zip

Package Zakura performance trace directories into zip archives with JSON manifests.

42|10|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/zakura-core/zakura --skill zakura-trace-zip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zakura-trace-zip
Source: https://github.com/zakura-core/zakura/tree/main/.agents/skills/zakura-trace-zip
Command: npx skills add https://github.com/zakura-core/zakura --skill zakura-trace-zip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill simplifies the process of bundling complex Zakura performance trace directories into shareable, structured archives, ensuring that all necessary diagnostic data is included for performance analysis.

Core Features & Use Cases

  • Automated Archiving: Automatically identifies and packages required JSONL trace files from a specified directory.
  • Contextual Inclusion: Optionally includes related benchmark logs, CSVs, and configuration files to provide a complete performance snapshot.
  • Manifest Generation: Automatically creates a JSON manifest within the archive to track metadata, file counts, and source information.
  • Use Case: When debugging a performance regression in a Zakura node, use this skill to package the trace directory and associated benchmark logs into a single zip file for team review.

Quick Start

Use the zakura-trace-zip skill to create a zip archive of the trace directory located at /path/to/traces and save it to the perf-artifacts folder.

Frequently Asked Questions about zakura-trace-zip

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

FAQPage Schema
How do I package performance trace directories into a zip archive for diagnostic sharing?

You can package performance trace directories into a zip archive by using a skill that automatically identifies JSONL trace files, includes associated benchmark logs, and generates a descriptive JSON manifest for metadata tracking.

What is the best way to bundle JSONL trace files and configuration data for performance debugging?

Bundling JSONL trace files and configuration data for performance debugging is best handled by an automated archiving process that collects all relevant diagnostic data into a single structured zip file for team review.

Do I need Python 3 to compress Zakura trace files and generate a manifest?

Yes, you need standard Python 3 libraries to validate trace structures, compress Zakura trace files, and automatically generate a JSON manifest tracking metadata and file counts within the archive.

Can I include benchmark logs and CSVs when archiving Zebra Zakura performance traces?

Yes, you can include benchmark logs and CSVs when archiving Zebra Zakura performance traces to provide a complete performance snapshot alongside the required JSONL trace files.

What limitations exist when archiving performance traces for a Zakura node regression?

Archiving performance traces for a Zakura node regression relies on standard Python 3 libraries and requires a specified trace directory; it focuses on packaging diagnostic data rather than analyzing the performance regression itself.

Does zakura-trace-zip work with standard Python libraries to validate trace structures?

Yes, zakura-trace-zip works with standard Python 3 libraries to validate trace structures, identify required JSONL trace files, and generate descriptive manifest files within the compressed zip archive.