Catalog
github/copilot-usage-metrics

github

copilot-usage-metrics

Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.

v1.0Latest
New~596Updated Jun 26, 2026

Copilot Usage Metrics

You are a skill that retrieves and displays GitHub Copilot usage metrics using the GitHub CLI (gh).

When to use this skill

Use this skill when the user asks about:

  • Copilot usage metrics, adoption, or statistics
  • How many people are using Copilot in their org or enterprise
  • Copilot acceptance rates, suggestions, or chat usage
  • Per-user Copilot usage breakdowns
  • Copilot usage on a specific date

How to use this skill

  1. Determine whether the user wants organization or enterprise level metrics.
  2. Ask for the org name or enterprise slug if not provided.
  3. Determine if they want aggregated metrics or per-user metrics.
  4. Determine if they want metrics for a specific day (YYYY-MM-DD format) or general/recent metrics.
  5. Run the appropriate script from this skill's directory.

Available scripts

Organization metrics

  • get-org-metrics.sh <org> [day] — Get aggregated Copilot usage metrics for an organization. Optionally pass a specific day in YYYY-MM-DD format.
  • get-org-user-metrics.sh <org> [day] — Get per-user Copilot usage metrics for an organization. Optionally pass a specific day.

Enterprise metrics

  • get-enterprise-metrics.sh <enterprise> [day] — Get aggregated Copilot usage metrics for an enterprise. Optionally pass a specific day.
  • get-enterprise-user-metrics.sh <enterprise> [day] — Get per-user Copilot usage metrics for an enterprise. Optionally pass a specific day.

Formatting the output

When presenting results to the user:

  • Summarize key metrics: total active users, acceptance rate, total suggestions, total chat interactions
  • Use tables for per-user breakdowns
  • Highlight trends if comparing multiple days
  • Note that metrics data is available starting from October 10, 2025, and historical data is accessible for up to 1 year

Important notes

  • These API endpoints require GitHub Enterprise Cloud.
  • The user must have appropriate permissions (enterprise owner, billing manager, or a token with manage_billing:copilot / read:enterprise scope).
  • The "Copilot usage metrics" policy must be enabled in enterprise settings.
  • If the API returns 403, advise the user to check their token permissions and enterprise policy settings.
Files5
5 files · 3.6 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

88

Quality

82

Clarity

85

Completeness

75

Summary

This skill retrieves and displays GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API. It provides four lightweight shell scripts that wrap `gh api` calls to fetch either aggregated or per-user metrics, with optional support for querying specific dates.

Detected Capabilities

github cli invocationrest api callsshell script executiondata retrieval and formattingparameter passing

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

copilot usage metricscopilot adoption ratecopilot per-user statsenterprise copilot usagegithub copilot analytics

Use Cases

  • Retrieve organization-level Copilot adoption and usage statistics
  • Get per-user Copilot metrics to understand individual contributor engagement
  • Query enterprise-wide Copilot metrics across multiple organizations
  • Analyze Copilot usage on specific dates for trend analysis or reporting
  • Monitor Copilot acceptance rates and chat interaction patterns

Quality Notes

  • Clear and well-structured documentation with distinct sections for use cases, available scripts, and important prerequisites
  • Scripts are simple, readable, and follow consistent patterns with proper error handling (set -euo pipefail)
  • Comprehensive prerequisites documentation (Enterprise Cloud requirement, permission scopes, policy settings)
  • Helpful guidance on output formatting and metric interpretation
  • All four scripts follow identical patterns and are self-documenting with header comments
  • Minor: No error handling guidance for common failure modes (invalid org/enterprise, expired tokens, insufficient permissions)
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/copilot-usage-metrics in your dev environment

Command Palette

Search for a command to run...