copilot-usage-metrics
Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
Works with
--- name: copilot-usage-metrics description: Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API. license: MIT --- # 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.
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

