repo-metrics

Track GitHub repository metrics as JSON time-series for trend analysis.

2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/adelpro/openclaw-arsenals --skill repo-metrics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-metrics
Source: https://github.com/adelpro/openclaw-arsenals/tree/main/02-skills/repo-metrics
Command: npx skills add https://github.com/adelpro/openclaw-arsenals --skill repo-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track GitHub repository metrics over time to capture engagement and activity.

Core Features & Use Cases

  • Time-series storage of repository metrics in JSON.
  • Trend reporting for Stars, Forks, Issues, and Traffic over days or weeks.
  • Daily snapshot capability across multiple repositories for dashboards and audits.

Quick Start

Create a daily metrics snapshot for your repository and append it to a JSON file for long-term trend analysis.

Frequently Asked Questions about repo-metrics

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

FAQPage Schema
How do I track GitHub repository metrics over time for trend analysis?▼

You track GitHub repository metrics over time by taking daily or periodic snapshots of stars, forks, issues, and traffic, then storing that data as JSON time-series for historical trend reporting.

What is the best way to automate daily GitHub repo metrics snapshots?▼

The best way to automate daily GitHub repo metrics snapshots is to apply an automated snapshot capability across individual or multiple repositories, appending the captured data into a JSON file for long-term trend analysis.

Can I generate trend reports for GitHub stars and traffic across multiple repositories?▼

Yes, you can generate trend reports for GitHub stars, forks, issues, and traffic across multiple repositories by applying daily snapshot capabilities to aggregate time-series data into dashboards and audits.

Does tracking GitHub metrics as JSON time-series require external dependencies?▼

Tracking GitHub metrics as JSON time-series requires no external dependencies, allowing you to directly store repository engagement and activity data for historical visibility without additional package installations.

What GitHub metrics can I capture for long-term historical visibility?▼

You can capture GitHub metrics including stars, forks, issues, and traffic for long-term historical visibility, storing the engagement and activity data as JSON time-series to support trend reporting over days or weeks.