Copilot Usage Metrics
Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
MCP get_skill({ skillId: "copilot-usage-metrics-4ded09be" })Use this skill with your agent
Create a free account and connect via MCP
# 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.
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Neon Performance Analyzer
Identify and fix slow Postgres queries automatically using Neon's branching workflow. Analyzes execution plans, tests optimizations in isolated database branches, and provides clear before/after performance metrics with actionable code fixes.
Performance Optimization Advisor
Produce a prioritized performance-optimization roadmap across frontend, backend, and infrastructure. Use as an explicit/manual helper after bottlenecks are known or suspected, not as the owner of regression detection, profiling capture, or test execution.
Qdrant Indexing Performance Optimization
Diagnoses and fixes slow Qdrant indexing and data ingestion. Use when someone reports 'uploads are slow', 'indexing takes forever', 'optimizer is stuck', 'HNSW build time too long', or 'data uploaded but search is bad'. Also use when optimizer status shows errors, segments won't merge, or indexing threshold questions arise.