Skip to main content
skillsSource-backedReview first Safety Privacy

Claude Code Analytics Adoption Capability Pack Skill

Expert Claude Code analytics adoption capability pack for enabling team and enterprise dashboards, GitHub contribution metrics, adoption tracking, ROI reporting, and OpenTelemetry complements with source-backed rollout steps.

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • This skill recommends analytics enablement steps; it must not toggle admin settings or install GitHub apps without explicit owner approval.
  • Contribution metrics are conservative underestimates and should not be treated as exact productivity scores for individuals.
  • Leaderboards and CSV exports can create unintended performance pressure; align rollout with HR and management policy first.
  • Zero Data Retention organizations cannot use GitHub contribution metrics; usage metrics only.
  • Console spend figures are estimates; use billing pages for actual costs.

Privacy notes

  • Analytics dashboards expose account emails, usage patterns, leaderboard rankings, and per-user spend or line counts depending on plan.
  • GitHub contribution metrics analyze merged PR diffs and Claude Code session activity within attribution windows; confirm code and identity visibility with security review.
  • CSV exports include all users, not just the top ten shown in the dashboard UI.
  • OpenTelemetry exports can replicate usage events into customer observability systems and need retention and access-control review.

Prerequisites

  • Claude for Teams, Claude for Enterprise, or Claude Console API access depending on the target dashboard.
  • Admin or Owner role for Team and Enterprise analytics setup, or UsageView permission for Console analytics.
  • GitHub admin access if enabling contribution metrics through the Claude GitHub app.
  • Clear rollout goals such as adoption tracking, ROI reporting, champion identification, or spend visibility.

Schema details

Install type
package
Reading time
9 min
Difficulty score
78
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-06-13
Retrieval sources
https://code.claude.com/docs/en/analyticshttps://code.claude.com/docs/en/champion-kithttps://code.claude.com/docs/en/communications-kithttps://code.claude.com/docs/en/admin-setuphttps://code.claude.com/docs/en/monitoring-usagehttps://code.claude.com/docs/en/zero-data-retentionhttps://code.claude.com/docs/en/skillshttps://github.com/anthropics/claude-codehttps://developers.google.com/search/docs/fundamentals/creating-helpful-content
Tested platforms
ClaudeClaude CodeCodexCursorWindsurfGeneric AGENTS
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Claude Code analytics adoption capability pack for this organization."

# Required output
1) Plan fit and dashboard target selection
2) Enablement checklist for analytics and GitHub contribution metrics
3) Adoption, ROI, and leaderboard interpretation guidance
4) ZDR and API-customer limitation notes
5) Privacy-safe rollout summary for admins and champions

About this resource

Knowledge Freshness

This capability pack is grounded in Claude Code analytics, champion kit, communications kit, admin setup, monitoring, zero data retention, and skills documentation verified on 2026-06-13. Contribution metrics remain in public beta; prefer live official docs when confirming plan availability.

Retrieval Sources

Source Verification Notes

Verified against official Claude Code analytics documentation on 2026-06-13:

  • Team and Enterprise analytics live at claude.ai/analytics/claude-code; Console API customers use platform.claude.com/claude-code.
  • Contribution metrics require the Claude GitHub app, admin enablement of GitHub analytics, and are unavailable for ZDR organizations.
  • Metrics are conservative underestimates; PRs are tagged when at least one high-confidence assisted line exists within a 21-day-before to 2-day-after merge attribution window.
  • Merged PRs containing assisted lines receive the claude-code-assisted GitHub label for programmatic lookup.
  • Console dashboard spend figures are estimates; billing pages show actual costs.

Scope Note

This is not a generic product-analytics framework. Use it when engineering leaders need a source-backed rollout plan for Claude Code analytics dashboards, GitHub contribution metrics, and complementary OpenTelemetry exports.

Core Workflow

  1. Select the dashboard lane:
    • Claude for Teams or Enterprise at claude.ai/analytics/claude-code
    • Claude Console API customers at platform.claude.com/claude-code
  2. Confirm prerequisites:
    • Team and Enterprise require Admin or Owner access.
    • Console requires UsageView permission.
    • Contribution metrics require Claude for Teams or Enterprise and do not apply to Console API-only customers.
  3. Enable base analytics:
    • Owners navigate to admin settings and enable Claude Code analytics.
  4. If contribution metrics are needed and ZDR is not enabled:
    • Install the Claude GitHub app on the target GitHub organization.
    • Enable GitHub analytics in admin settings.
    • Complete GitHub authentication and select included organizations.
  5. Set expectations for data latency: contribution data typically appears within 24 hours with daily updates.
  6. Review summary metrics and chart lanes:
    • Adoption: daily active users and sessions
    • Contribution: PRs and lines with Claude Code assistance
    • Accept rate and accepted lines from editing tools
    • Leaderboard and CSV export for champions or broader reporting
  7. Interpret attribution conservatively:
    • PRs tagged when at least one high-confidence assisted line exists
    • 21-day-before to 2-day-after merge attribution window
    • Excluded lockfiles, generated artifacts, and heavily rewritten code
  8. Plan complementary telemetry:
    • OpenTelemetry export for per-user token counts and cost estimates on Team and Enterprise
    • Console team insights for per-member spend and line counts
  9. Pair analytics rollout with champion and communications kits for adoption, not just measurement.

Capability Scope

  • Dashboard selection for Team, Enterprise, and Console API customers.
  • Analytics and GitHub contribution metric enablement checklist.
  • Adoption, ROI, and leaderboard interpretation guidance.
  • ZDR and API-customer limitation awareness.
  • OpenTelemetry complement planning.
  • Privacy-safe admin and champion rollout notes.

Compatibility

Native

  • Claude Code / Claude: use as an Agent Skill when planning analytics rollout, admin setup, or internal ROI reporting for Claude Code.

Manual Adaptation

  • Codex, Cursor, Windsurf, and Generic AGENTS workflows: use the workflow as a checklist for Claude Code analytics adoption planning in platform teams.

Required Inputs

  • Plan type, admin roles available, and whether ZDR is enabled.
  • GitHub organization scope and admin access for contribution metrics.
  • Rollout goals: adoption, ROI, spend visibility, champion program, or export.
  • Whether Console API usage outside the claude.ai org must be measured separately.

Production Rules

  • Do not use leaderboard rankings as performance review inputs without policy alignment.
  • Treat contribution metrics as conservative underestimates, not exact credit.
  • Do not promise GitHub contribution metrics for ZDR orgs or Console-only API customers.
  • Use billing pages for actual spend; dashboard spend is estimated on Console.
  • Restrict CSV exports and OpenTelemetry sinks to approved audiences.
  • Combine analytics with champion-kit and communications-kit messaging for adoption, not surveillance framing.
  • Redact user emails and internal repo names in public rollout examples.

Review Matrix

Goal Route Limitation
Track daily adoption Adoption chart Team/Enterprise dashboard
Measure assisted PR volume Contribution metrics Requires GitHub app; unavailable under ZDR
Identify champions Leaderboard or CSV export Handle sensitively with HR policy
Per-user token cost detail OpenTelemetry export Complements dashboard on Team/Enterprise
API spend by member Console team insights Contribution metrics not available
Programmatic PR lookup GitHub label search Use claude-code-assisted label

Output Contract

  1. Dashboard lane and role requirement summary.
  2. Enablement checklist with GitHub and admin steps.
  3. Metric interpretation notes and known limitations.
  4. Complementary OpenTelemetry or billing follow-ups.
  5. Champion and communications rollout recommendations.
  6. Privacy-safe summary suitable for admin review or internal launch docs.

Duplicate Check

Checked content/skills, content/guides, generated catalog text, and open pull requests for Claude Code analytics adoption, dashboard setup, and GitHub contribution metric workflows. Official docs and champion materials exist, but no skills entry provides a reusable analytics adoption capability pack with enablement checklist and limitation matrix.

Editorial Disclosure

Submitted as an independent source-backed HeyClaude content entry by kiannidev. It is based on public Claude Code documentation, the public Anthropic claude-code repository, and Google Search Central helpful-content guidance. No paid placement, referral link, affiliate link, or vendor sponsorship is used.

Source citations

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.