PlugWiki

copilot-usage-metrics Skill (awesome-copilot): Pull GitHub Copilot Usage Metrics

Pulls GitHub Copilot usage metrics for an organization or enterprise through the GitHub CLI and summarizes them.

Installs
8.7K
on skills.sh
Stars
40.7K
on GitHub
Files
4
besides SKILL.md
Updated
Oct 2026
last repo commit

This skill runs four small scripts that call the GitHub API through gh. It returns Copilot usage for an organization or an enterprise, either as totals or per user, for a day you name or for the recent period.

It then summarizes active users, acceptance rate, suggestions and chat use. It needs GitHub Enterprise Cloud and a signed-in gh account with the right permissions. Ask for the org name or enterprise slug first.

Good for

  • Engineering managers tracking Copilot adoption in their org
  • Enterprise owners and billing managers checking usage on a given day
  • Admins who need a per-user usage breakdown

Install copilot-usage-metrics

Claude Code

  1. 1

    Download the skill folder from https://github.com/github/awesome-copilot/tree/HEAD/skills/copilot-usage-metrics.

  2. 2

    Put it at ~/.claude/skills/copilot-usage-metrics/ so that SKILL.md sits directly inside.

  3. 3

    Start a new session; the skill loads when its description matches the task.

Requires GitHub CLI (gh), signed in.

Keep the four .sh files in the folder with SKILL.md. The skill runs them from its own directory with the GitHub CLI, so there is no Claude app upload route. The data needs GitHub Enterprise Cloud.

Built from the package data we hold. Not yet tested by us.

What's in the skill

When it loads

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

Sections in SKILL.md

  1. When to use this skill
  2. How to use this skill
  3. Available scripts
  4. Organization metrics
  5. Enterprise metrics
  6. Formatting the output
  7. Important notes

Key facts

License
MIT
Installs on skills.sh
8,724 (Nov 2, 2026)
Last repo commit
Oct 30, 2026

What it includes

  • Aggregated Copilot usage for an organization, optionally for one day (YYYY-MM-DD).

    Runs gh api against /orgs/<org>/copilot/usage, or /usage/day?day=<day>.

    Try: “Show Copilot usage for the acme org yesterday”

    Runs code · get-org-metrics.sh <org> [day]

  • Per-user Copilot usage for an organization, optionally for one day.

    Runs gh api against /orgs/<org>/copilot/usage/users, or /users/day?day=<day>.

    Runs code · get-org-user-metrics.sh <org> [day]

  • Aggregated Copilot usage for an enterprise, optionally for one day.

    Runs gh api against /enterprises/<enterprise>/copilot/usage, or /usage/day?day=<day>.

    Runs code · get-enterprise-metrics.sh <enterprise> [day]

  • Per-user Copilot usage for an enterprise, optionally for one day.

    Runs gh api against /enterprises/<enterprise>/copilot/usage/users, or /users/day?day=<day>.

    Runs code · get-enterprise-user-metrics.sh <enterprise> [day]

  • Summarizes active users, acceptance rate, suggestions and chat use; tables per user.

    It notes that data starts October 10, 2025 and goes back up to one year.

    Output formatting

  • On a 403 it tells you to check your token permissions and enterprise policy settings.

    403 guidance

From the official docs

Permissions

Low risk

It runs shell scripts that call the GitHub API with your gh login and can return per-user usage. Use an account scoped to what you need.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Per-user scripts return individual usage

    get-org-user-metrics.sh and get-enterprise-user-metrics.sh list usage per person. Check your company policy before you share that output. github.com

  • It runs shell scripts with your gh login

    Each of the four scripts calls gh api. Read them first; they are short. Use an account scoped to what you need. github.com

Technical details
Turning on read-onlyNo switch. Each script runs one gh api call to a copilot/usage path.
Talks toapi.github.com (through gh api)
Scopes
  • Uses your gh login; the SKILL.md names manage_billing:copilot and read:enterprise as token scopes

  • Reads org or enterprise Copilot usage, including per-user usage

Questions

What does copilot-usage-metrics do?

It makes your assistant pull GitHub Copilot usage numbers for an organization or an enterprise with the GitHub CLI, and summarize them. You can ask for totals or for a per-user breakdown, for one day or in general.

What do I need to use it?

The GitHub CLI (gh) signed in to an account that can see the data. The SKILL.md says these endpoints require GitHub Enterprise Cloud, and the user must be an enterprise owner, a billing manager, or hold a token with the manage_billing:copilot or read:enterprise scope. The "Copilot usage metrics" policy must be on in enterprise settings.

How do I install it?

Use the install box above. Keep the four .sh files in the folder with SKILL.md, because the skill runs them from its own directory.

How far back does the data go?

The SKILL.md says metrics are available starting from October 10, 2025, and historical data is accessible for up to 1 year.

Is it safe?

Each script makes one gh api call to GitHub using your signed-in account. The per-user scripts return usage for individual people, so share the output with care.

Does it work in the Claude app?

The install box has no Claude app upload tab because the skill runs shell scripts and the gh CLI on your machine. It fits an agent that can run commands.

Information

updated Nov 2, 2026

Folder
skills/copilot-usage-metrics

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. copilot-usage-metrics SKILL.md · github.com
  2. get-org-metrics.sh · github.com
  3. get-org-user-metrics.sh · github.com
  4. get-enterprise-metrics.sh · github.com
  5. get-enterprise-user-metrics.sh · github.com
  6. LICENSE · github.com

Updated Nov 2, 2026.