Skip to content
Get packs

Guide · Agent skill

How to use the Copilot Usage Metrics agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The copilot-usage-metrics skill teaches an AI agent to fetch GitHub Copilot usage statistics for a GitHub organization or enterprise and summarize them, including active users, acceptance rate, suggestions and chat interactions. It is aimed at engineering managers, admins and enterprise billing managers who want to see how much their team uses Copilot. After this guide you will know how to install the skill, ask for metrics in plain language, and what your GitHub account needs for the API to return data.

Copilot Usage Metricsgithub/awesome-copilot · MIT

Quick start

  1. 1Confirm requirements. Check that you have GitHub Enterprise Cloud, an authenticated GitHub CLI, and a token with the right scope or role.
  2. 2Enable the policy. Make sure the 'Copilot usage metrics' policy is enabled in your enterprise settings.
  3. 3Download and unzip. Download the skill ZIP from our page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder.
  4. 4Or upload in the Claude apps. Alternatively, go to Settings → Capabilities → Skills in the Claude apps and upload the skill.
  5. 5Ask a natural question. Ask about Copilot usage for your org or enterprise, naming the org or enterprise slug.
  6. 6Choose the level of detail. Say whether you want aggregated totals or a per-user table, and optionally a specific day in YYYY-MM-DD format.

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file and optional scripts that an AI agent can load when a task matches the skill's description. This one is for GitHub Copilot usage data.

When you ask about Copilot adoption, the agent runs one of four small shell scripts. Each script calls GitHub's REST API through the GitHub CLI (gh). The agent then summarizes the results and can show per-user breakdowns in tables. It can also target a specific date in YYYY-MM-DD format.

  • Organization or enterprise level, depending on what you ask for
  • Aggregated totals or per-user breakdowns
  • General recent metrics or a single named day

Install the Copilot Usage Metrics skill

Download the ZIP for the skill from our page and unzip it. For a personal install, place the folder in ~/.claude/skills/. For a single project, place it in the project's .claude/skills/ folder.

You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.

  • Personal: ~/.claude/skills/copilot-usage-metrics
  • Project: .claude/skills/copilot-usage-metrics

Check the requirements before you start

The skill only works if your GitHub setup meets several conditions. The API endpoints it uses require GitHub Enterprise Cloud. Without it, no data is returned.

You also need the GitHub CLI installed and authenticated, a Bash-compatible shell, and a token with the manage_billing:copilot or read:enterprise scope, or the enterprise owner or billing manager role. The 'Copilot usage metrics' policy must be enabled in enterprise settings.

  • GitHub CLI (gh) installed and authenticated
  • Bash-compatible shell
  • GitHub Enterprise Cloud
  • Token with manage_billing:copilot or read:enterprise scope, or enterprise owner/billing manager role
  • 'Copilot usage metrics' policy enabled in enterprise settings

Trigger the skill with natural requests

You do not need to name the scripts. The agent uses the skill when you ask about Copilot usage metrics, adoption, acceptance rates, suggestions, chat usage, per-user breakdowns, or usage on a specific date.

The agent may ask for your org name or enterprise slug if you leave it out, and it will ask whether you want aggregated or per-user metrics.

  • "How many people are using Copilot in the acme org?"
  • "What was the Copilot acceptance rate for our enterprise yesterday?"
  • "Show a per-user Copilot usage table for the platform org."
  • "Copilot usage for enterprise my-enterprise on 2025-11-03."

What the scripts do

The skill includes four scripts, one for each combination of level and detail. Each takes a required org or enterprise name and an optional day.

  • get-org-metrics.sh <org> [day]: aggregated organization metrics
  • get-org-user-metrics.sh <org> [day]: per-user organization metrics
  • get-enterprise-metrics.sh <enterprise> [day]: aggregated enterprise metrics
  • get-enterprise-user-metrics.sh <enterprise> [day]: per-user enterprise metrics
get-org-metrics.sh <org> [day]

Safety notes: scripts and network access

This skill runs shell scripts and uses the network to call the GitHub API. Read the scripts in the skill folder before you install it, especially if you did not write the skill yourself. The skill is MIT licensed.

Your token gives the agent access to billing and usage data for your organization or enterprise. Use a token with the narrowest scope that works and avoid sharing it in chat.

  • The skill runs scripts on your machine.
  • The skill makes network calls to GitHub's REST API.
  • Metrics data is available starting from October 10, 2025, and historical data is accessible for up to 1 year.

Tips and troubleshooting

If the API returns a 403 error, the skill advises you to check your token permissions and your enterprise policy settings. Most 403 errors come from a missing scope, a role that is not owner or billing manager, or the Copilot usage metrics policy being off.

When comparing several days, ask the agent to highlight trends. Ask for tables when you need per-user numbers.

  • Check that gh is authenticated before asking for metrics.
  • Give the exact org name or enterprise slug to avoid ambiguity.
  • Use YYYY-MM-DD for specific dates.
  • Remember that per-user data is only available through the user-level scripts.

What people use it for

  • Checking how many people in an engineering org actively used Copilot this week
  • Comparing acceptance rates on two specific days
  • Building a per-user table to see which team members use chat
  • Tracking Copilot adoption across an enterprise for a billing review

Frequently asked questions

How do I install the copilot usage metrics skill?

Download the ZIP from our page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings → Capabilities → Skills.

What do I need to use the copilot usage metrics skill?

You need the GitHub CLI (gh) installed and authenticated, a Bash-compatible shell, and GitHub Enterprise Cloud. You also need a token with manage_billing:copilot or read:enterprise scope, or the enterprise owner or billing manager role, and the Copilot usage metrics policy enabled.

Does this skill work with a personal GitHub account or individual Copilot subscription?

No. The skill targets organization and enterprise level data, and the endpoints it relies on require GitHub Enterprise Cloud. Individual subscribers cannot access this data through the skill.

Why does the skill return a 403 error?

A 403 usually means your token lacks the required scope, your account is not an enterprise owner or billing manager, or the Copilot usage metrics policy is not enabled. The skill advises checking token permissions and enterprise policy settings.

Is the copilot usage metrics skill free?

The skill is released under the MIT licence. Access to the underlying data depends on your GitHub Enterprise Cloud plan, which this source does not price.

How far back can I get Copilot usage data?

According to the skill, metrics data is available starting from October 10, 2025, and historical data is accessible for up to 1 year.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits engineering managers, admins and enterprise billing managers who already run GitHub Enterprise Cloud and want quick Copilot usage summaries without writing API calls. If you are on a personal account or an individual Copilot plan, or lack admin, billing or the right token scope, it will not return data, so use GitHub's own usage pages or a different approach instead.

Download the skill