speckit-token-analyzer-report

Name: speckit-token-analyzer-report
Availability: InStock
Author: Kami

Generate markdown or JSON token analysis reports from Spec Kit run data.

Updated May 18, 2026

Search Tags:#report generation #token analysis #markdown report #spec kit #workflow metrics #cross-run comparison

Ready to run

npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-token-analyzer-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-token-analyzer-report
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-token-analyzer-report
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-token-analyzer-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn raw token-analysis runs into a readable report so you can understand where tokens are spent, compare runs, and identify optimization opportunities without manually stitching together run files.

Core Features & Use Cases

Run aggregation: Combines one or more captured runs into a single analysis view.
Cross-run comparison: Summarizes totals, averages, standard deviation, and quality scores across runs.
Optimization guidance: Highlights the biggest token consumers and suggests where to reduce overhead or improve efficiency.
Use case: Use it after several Spec Kit workflow runs to produce a markdown report for review, sharing, or planning the next optimization pass.

Quick Start

Ask for a token analysis report named after your scenario and include any specific run labels or output format you want.

Frequently Asked Questions about speckit-token-analyzer-report

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

FAQPage Schema

How do I generate a markdown report from token analysis runs?▼

To generate a markdown report from token analysis runs, you need to provide captured run metadata, summary totals, and step-level JSON inputs. The tool aggregates this data to produce a readable markdown or JSON deliverable summarizing your token usage.

What is the best way to compare token usage across multiple Spec Kit workflow runs?▼

The best way to compare token usage across multiple Spec Kit workflow runs is to aggregate the captured run data. The tool calculates totals, averages, and standard deviations to provide a cross-run comparison view for your scenarios.

Can I identify token optimization opportunities from per-step metrics?▼

Yes, you can identify token optimization opportunities from per-step metrics. The analysis highlights the biggest token consumers in your workflow and suggests where to reduce overhead or improve efficiency based on the captured run data.

What inputs are required to produce a token analysis report?▼

Producing a token analysis report requires run metadata, summary totals, step-level JSON inputs, and report templating. These elements are necessary to aggregate the data and generate the final markdown or JSON deliverable.

When do I need a cross-run comparison report for my token usage?▼

You need a cross-run comparison report when you have completed several Spec Kit workflow runs and want to understand where tokens are spent. It helps you review performance, share insights, and plan your next optimization pass.

Does the token analysis report work with raw run files without manual stitching?▼

Yes, the token analysis report works with raw run files by combining one or more captured runs into a single analysis view. This prevents you from manually stitching together run files to understand your workflow metrics.