copilot-usage-metrics
github/awesome-copilot
Pull GitHub Copilot adoption and usage stats for your org or enterprise straight from the CLI.
What is copilot-usage-metrics?
This skill retrieves and displays GitHub Copilot usage metrics for organizations and enterprises via the GitHub CLI and REST API. Use it to answer questions about Copilot adoption, acceptance rates, suggestion counts, chat usage, and per-user breakdowns, optionally for a specific date.
- Fetches aggregated Copilot usage metrics for an organization or enterprise
- Fetches per-user Copilot usage metrics for an organization or enterprise
- Supports querying metrics for a specific day in YYYY-MM-DD format
- Formats output with summaries of active users, acceptance rate, suggestions, and chat interactions
- Presents per-user data in tables and highlights trends across days
How to install copilot-usage-metrics
npx skills add https://github.com/github/awesome-copilot --skill copilot-usage-metrics- GitHub CLI (gh) installed and authenticated
- GitHub Enterprise Cloud account
- Enterprise owner, billing manager role, or a token with manage_billing:copilot / read:enterprise scope
- 'Copilot usage metrics' policy enabled in enterprise settings
How to use copilot-usage-metrics
- 1.Determine whether you want organization-level or enterprise-level Copilot usage metrics
- 2.Identify the org name or enterprise slug to query
- 3.Decide whether you want aggregated metrics or per-user breakdowns
- 4.Decide whether you want metrics for a specific day (YYYY-MM-DD) or general/recent data
- 5.Run the corresponding script (get-org-metrics.sh, get-org-user-metrics.sh, get-enterprise-metrics.sh, or get-enterprise-user-metrics.sh) with the org/enterprise and optional day argument
- 6.Review the formatted output, including summarized key metrics and per-user tables where applicable
Use cases
- Checking how many users are actively using Copilot in an organization
- Reviewing Copilot acceptance rates and suggestion counts across an enterprise
- Getting a per-user breakdown of Copilot chat and suggestion usage
- Pulling Copilot usage metrics for a specific historical date
- Comparing Copilot usage trends across multiple days
- Enterprise owners and billing managers tracking Copilot adoption
- Engineering managers evaluating Copilot ROI and usage
- DevOps/IT admins monitoring Copilot rollout across teams
- Platform teams reporting on developer tool adoption
copilot-usage-metrics FAQ
You need to be an enterprise owner, billing manager, or have a token with manage_billing:copilot or read:enterprise scope. The 'Copilot usage metrics' policy must also be enabled in enterprise settings.
Check your token permissions and enterprise policy settings; access requires GitHub Enterprise Cloud and the proper scopes/permissions.
Metrics data is available starting from October 10, 2025, and historical data is accessible for up to 1 year.
Yes, all scripts accept an optional day argument in YYYY-MM-DD format to retrieve metrics for that specific date.
No, these API endpoints require GitHub Enterprise Cloud.
Full instructions (SKILL.md)
Source of truth, from github/awesome-copilot.
name: copilot-usage-metrics description: Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
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
- Determine whether the user wants organization or enterprise level metrics.
- Ask for the org name or enterprise slug if not provided.
- Determine if they want aggregated metrics or per-user metrics.
- Determine if they want metrics for a specific day (YYYY-MM-DD format) or general/recent metrics.
- 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:enterprisescope). - 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.
Related skills
More from github/awesome-copilot and the wider catalog.
git-commit
Execute semantic git commits with conventional message analysis and intelligent staging.
excalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions.
documentation-writer
Create structured technical documentation using the Diátaxis framework for tutorials, how-to guides, references, and explanations.
gh-cli
GitHub CLI comprehensive reference for repositories, issues, PRs, Actions, projects, releases, and all GitHub operations from the command line.
prd
Generate comprehensive Product Requirements Documents with executive summaries, user stories, technical specs, and risk analysis.
refactor
Surgical code refactoring to improve maintainability without changing behavior.