Copilot Usage Metrics
Pull GitHub Copilot org or enterprise usage metrics (adoption, acceptance, chat) via `gh` and bundled shell scripts for a given day or recent window.
Overview
copilot-usage-metrics is an agent skill most often used in Grow (also Operate monitoring) that fetches and displays GitHub Copilot usage metrics for organizations and enterprises using `gh` and packaged shell scripts.
Install
npx skills add https://github.com/github/awesome-copilot --skill copilot-usage-metricsWhat is this skill?
- Org-level scripts: `get-org-metrics.sh` and `get-org-user-metrics.sh` with optional YYYY-MM-DD day filter
- Enterprise-level scripts: `get-enterprise-metrics.sh` and enterprise per-user variants via GitHub REST + `gh`
- Clarifies org vs enterprise scope, aggregated vs per-user, and single-day vs general metrics
- Covers acceptance rates, suggestions, and chat usage questions users typically ask
- Stepped workflow: infer scope, collect org/enterprise slug, then run the matching script from the skill directory
Adoption & trust: 8.5k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Copilot adoption or acceptance numbers for your org or enterprise but do not want to click through admin panels or hand-craft REST calls every time.
Who is it for?
Engineering leads at indie SaaS shops or small orgs who already use `gh` and need quick Copilot ROI snapshots.
Skip if: Builders without GitHub org/enterprise admin or metrics API access, or teams that only need generic GitHub Actions usage (not Copilot-specific).
When should I use this skill?
User asks about Copilot usage metrics, adoption, acceptance rates, per-user breakdowns, or metrics for a specific date at org or enterprise level.
What do I get? / Deliverables
You get script-driven aggregated or per-user Copilot metrics for the slug and date you specify, ready to paste into reports or standups.
- Terminal output from org or enterprise Copilot metrics scripts
- Clarified report scope (aggregated vs per-user, day vs recent)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Copilot adoption and suggestion acceptance are growth and tooling ROI signals, so the canonical shelf is Grow analytics even though engineering leads also check them during operations. Analytics fits aggregated and per-user Copilot metrics, date-scoped queries, and acceptance-rate reporting—not writing product code.
Where it fits
Pull aggregated org Copilot metrics before a monthly growth retro on engineering velocity.
Check per-user Copilot usage after onboarding new contractors to spot idle seats.
Verify suggestion acceptance stayed stable during a release week crunch.
How it compares
Skill-wrapped `gh` scripts for Copilot metrics—not an MCP server and not a substitute for GitHub’s full Insights product UI.
Common Questions / FAQ
Who is copilot-usage-metrics for?
Solo founders and small teams managing GitHub Copilot at org or enterprise scale who want agents to run standardized metrics scripts instead of ad-hoc API exploration.
When should I use copilot-usage-metrics?
Use it in Grow when reviewing adoption and acceptance trends; in Operate when monitoring seat utilization; or before launch/ship checkpoints when validating that the team is actually using Copilot on new repos.
Is copilot-usage-metrics safe to install?
It runs shell scripts and calls GitHub with your credentials—review the Security Audits panel on this page, scope `gh` tokens minimally, and avoid running per-user exports in untrusted agent environments.
SKILL.md
READMESKILL.md - Copilot Usage Metrics
# 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. #!/usr/bin/env bash # Fetch per-user Copilot usage metrics for an organization # Usage: get-org-user-metrics.sh <org> [day] # org - GitHub organization name # day - (optional) specific day in YYYY-MM-DD format set -euo pipefail ORG="${1:?Usage: get-org-user-metrics.sh <org> [day]}" DAY="${2:-}" if [ -n "$DAY" ]; then gh api \ -H "Accept: application/vnd.github+json" \ -H "X-GitHub-Api-Version: 2022-11-28" \ "/orgs/$ORG/copilot/usage/users/day?day=$DAY" else gh api \ -H "Accept: application/vnd.github+json" \ -H "X-GitHub-Api-Version: 2022-11-28" \ "/orgs/$ORG/copilot/usage/users" fi #!/usr/bin/env bash # Fetch aggregated Copilot usage metrics for an enterprise # Usage: get-enterprise-metrics.sh <enterprise> [day] # enterprise - GitHub enterprise slug # day - (optional) specific day in YYYY-MM-DD format set -euo pipefail ENTERPRISE="${1:?Usage: get-enterprise-metrics.sh <enterprise> [day]}" DAY="${2:-}" if [ -n "$DAY" ]; then gh api \ -H "Accept: application/vnd.github+json" \ -H "X-GitHub-Api-Version: 2022-11-28" \ "/enterprises/$ENTERPRISE/copilot/usage/day?day=$DAY" else gh api \ -H "Accept: application/vnd.github+json" \ -H "X-GitHub-Api-Version: 2022-11-28" \ "/enterprises/$ENTERPRISE/copilot/usage" fi #!/usr/bin/env bash # Fetch per-user Copilot usage metrics for an enterprise # Usage: get-enterprise-user-metrics.sh <enterprise> [day] # enterprise - GitHub enterprise slug # day - (optional) specific day in YYYY-MM-DD format set -euo pipefail