usage-analytics

Analyze subagent and skill usage logs to identify adoption patterns and failures.

13|5|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Jonghakseo/my-pi --skill usage-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usage-analytics
Source: https://github.com/Jonghakseo/my-pi/tree/main/skills/usage-analytics
Command: npx skills add https://github.com/Jonghakseo/my-pi --skill usage-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify usage patterns, failures, underused agents, and inactive skills from activity logs so teams can make evidence-based improvements to their development environment.

Core Features & Use Cases

  • Usage Measurement: Analyze subagent calls, success and failure rates, execution times, models, modes, and daily trends.
  • Skill Adoption Analysis: Separately measure explicit skill invocations and direct reads, including last-use dates and inactive skills.
  • Actionable Insights: Detect overuse, low adoption, high error rates, context overflow, excessive tool output, and other optimization opportunities.
  • Use Case: Review the past 30 days of activity to identify unreliable agents, unused skills, and concrete configuration or workflow improvements.

Quick Start

Ask the usage-analytics skill to analyze the recent seven days of subagent and skill usage data and summarize the key recommendations.

Frequently Asked Questions about usage-analytics

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

FAQPage Schema
How do I analyze subagent usage logs to identify failures and inefficiencies?

Analyze subagent usage logs by processing the JSONL activity data to identify adoption patterns, failure rates, and execution times. This isolates unreliable agents, detects context overflow, and highlights workflow optimization opportunities for your development environment.

What's the best way to detect inactive skills and low adoption from activity logs?

Detect inactive skills by measuring explicit skill invocations and direct reads from the usage analytics JSONL log. This separates invocation metrics from read activity, calculates last-use dates, and flags underutilized skills for configuration improvements.

How do I review agent performance metrics and error rates over a specific time period?

Review agent performance metrics by filtering the usage analytics JSONL log and registered agent directories by your target period. This separates daily trend metrics, success rates, and execution models to compare usage frequency and pinpoint high-error subagents.

Can I use usage analytics to find optimization opportunities for excessive tool output and context overflow?

Usage analytics identifies optimization opportunities by processing activity logs to detect context overflow, excessive tool output, and overuse patterns. This yields actionable insights to refine subagent configurations and improve overall workflow efficiency.

Do I need registered agent and skill directories to perform time-based trend analysis on usage logs?

Registered agent and skill directories are required alongside the usage analytics JSONL log for accurate time-based trend analysis. These directories enable precise period filtering, metric separation, and valid usage comparisons across your development environment.

Why does my subagent usage analysis show high error rates and unreliable execution?

High error rates in subagent usage analysis emerge from processing activity logs that track failure rates, execution times, and context overflow. Identifying these patterns reveals unreliable agents and pinpoints concrete configuration or workflow improvements needed.