Source profileQuality 83/100Review permissions

github/awesome-copilot/skills/copilot-usage-metrics/SKILL.md

copilot-usage-metrics

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

Source repository stars
37,126
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

  • Copilot usage metrics, adoption, or statistics
  • How many people are using Copilot in their org or enterprise
  • Copilot acceptance rates, suggestions, or chat usage

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/github/awesome-copilot --skill "skills/copilot-usage-metrics"
Safe inspection promptEditorial

Inspect the Agent Skill "copilot-usage-metrics" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/copilot-usage-metrics/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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…

    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.
  2. 02

    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

    Copilot usage metrics, adoption, or statisticsHow many people are using Copilot in their org or enterpriseCopilot acceptance rates, suggestions, or chat usage
  3. 03

    Available scripts

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

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

    Organization metrics

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

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

Permission review

Static risk signals and limitations

Runs scripts

medium · line 20

The documentation asks the agent to run terminal commands or scripts.

Run the appropriate script from this skill's directory.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score83/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars37,126SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
github/awesome-copilot
Skill path
skills/copilot-usage-metrics/SKILL.md
Commit
9933dcad5be5caeb288cebcd370eeeb2fc2f1685
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.

Alternatives

Compare before choosing

Computed 10042,015

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

2026-07-270 platforms
Computed 1007

event4u-app/agent-config

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

2026-07-280 platforms
Computed 1007

event4u-app/agent-config

existing-ui-audit

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

2026-07-280 platforms
Computed 1007

event4u-app/agent-config

testing-anti-patterns

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

2026-07-280 platforms