analytics

Aggregate and visualize CLI tool usage statistics from telemetry metrics.

1|Updated Feb 5, 2026

Search Tags:#analytics #cli #metrics #dashboard #visualization #statistics #telemetry

Ready to run

npx skills add https://github.com/tygwan/ultra-codex-init --skill analytics-tygwan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analytics
Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/analytics
Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill analytics-tygwan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analysts and teams struggle to quickly understand how tools are used across a CLI-based environment. This skill provides a concise, real-time visualization of tool usage so stakeholders can spot trends and bottlenecks.

Core Features & Use Cases

CLI Visualization: renders bar charts, sparklines, and distribution graphs from metrics data.
Usage Monitoring: track tool invocation counts, errors, and activity over time.
Use Case: project managers can audit tool adoption and identify underutilized commands across teams.

Quick Start

Run the analytics skill to generate an immediate CLI usage dashboard from the metrics file.

Frequently Asked Questions about analytics

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

FAQPage Schema

How do I visualize CLI telemetry and tool usage statistics in the terminal?▼

You can visualize CLI telemetry by running an analytics skill that aggregates tool invocation data from a metrics file and renders bar charts, sparklines, and distribution graphs directly in the terminal.

What do I need to generate a CLI usage dashboard for monitoring tool activity?▼

To generate a CLI usage dashboard, you need a metrics source at .codex/analytics/metrics.jsonl, a visualization script at .codex/scripts/analytics-visualizer.sh, and configuration settings in .codex/settings.json.

Can I track tool invocation counts and errors over time from command line metrics?▼

Yes, you can track tool invocation counts and errors over time by applying this skill to environments that collect tool invocation data, rendering usage statistics into real-time CLI charts.

What is the best way to spot trends and bottlenecks in tool adoption across teams?▼

The best way to spot trends and bottlenecks in tool adoption is to render concise, real-time visualizations of tool usage statistics, allowing project managers to audit activity and identify underutilized commands.

Does this CLI analytics visualization work without a dedicated metrics collection source?▼

No, this CLI analytics visualization requires a metrics source file collecting tool invocation data, as it aggregates and visualizes existing statistics rather than generating the telemetry itself.

Why are my tool usage charts and sparklines not rendering in the CLI dashboard?▼

Tool usage charts may not render if the metrics file at .codex/analytics/metrics.jsonl is missing, or if the visualization script at .codex/scripts/analytics-visualizer.sh lacks proper configuration in .codex/settings.json.