Retrieve and display GitHub Copilot usage metrics for organizations and enterprises.
Works with
Supports both organization-level and enterprise-level metrics queries, with optional filtering by specific date (YYYY-MM-DD format)
Provides aggregated metrics (total active users, acceptance rates, suggestions, chat interactions) and per-user breakdowns via separate commands
Requires GitHub Enterprise Cloud, appropriate token permissions ( manage_billing:copilot or read:enterprise scope), and the \"
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncopilot-usage-metricsExecute the skills CLI command in your project's root directory to begin installation:
Fetches copilot-usage-metrics from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate copilot-usage-metrics. Access via /copilot-usage-metrics in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
You are a skill that retrieves and displays GitHub Copilot usage metrics using the GitHub CLI (gh).
Use this skill when the user asks about:
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.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.When presenting results to the user:
manage_billing:copilot / read:enterprise scope).Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
copilot-usage-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for copilot-usage-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.
copilot-usage-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
copilot-usage-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: copilot-usage-metrics is focused, and the summary matches what you get after install.
Registry listing for copilot-usage-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.
copilot-usage-metrics has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in copilot-usage-metrics — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend copilot-usage-metrics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added copilot-usage-metrics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 31