Monitor Windsurf AI adoption, feature usage, and team productivity metrics.
Use when tracking AI feature usage, measuring ROI, setting up dashboards,
or analyzing Cascade effectiveness across your team.
Trigger with phrases like "windsurf monitoring", "windsurf metrics",
"windsurf analytics", "windsurf usage", "windsurf adoption".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
windsurf-observability
description
Monitor Windsurf AI adoption, feature usage, and team productivity metrics.
Use when tracking AI feature usage, measuring ROI, setting up dashboards,
or analyzing Cascade effectiveness across your team.
Trigger with phrases like "windsurf monitoring", "windsurf metrics",
"windsurf analytics", "windsurf usage", "windsurf adoption".
Designed for Claude Code, also compatible with Codex and OpenClaw
Windsurf Observability
Overview
Monitor Windsurf AI IDE adoption, feature usage, and productivity impact across your team. Covers Admin Dashboard analytics, custom tracking via extensions, and ROI measurement.
Prerequisites
Windsurf Teams or Enterprise plan
Admin dashboard access at windsurf.com/dashboard
Team members actively using Windsurf
Instructions
Step 1: Access Admin Dashboard Analytics
Navigate to Admin Dashboard > Analytics for team-wide metrics:
# Key metrics available in Windsurf Admin Dashboardcore_metrics:adoption:active_users_daily:"Unique developers using Windsurf per day"seat_utilization:"Active users / total seats (target: >80%)"feature_adoption:"Which AI features each user uses"quality:completion_acceptance_rate:"Supercomplete suggestions accepted vs shown"cascade_flow_success_rate:"Cascade tasks completed vs failed"consumption:credits_consumed_per_user:"Monthly credit usage per team member"credits_by_model:"Which AI models consume the most credits"efficiency:tasks_per_session:"Average Cascade interactions per session"time_saved_estimate:"Based on task complexity and completion speed"
Step 2: Set Up Usage Alerts
Monitor for underutilization and overuse:
# Alert thresholds for team managementalerts:low_adoption:condition:"seat_utilization < 50% for 7 days"action:"Schedule team training session"
low_acceptance_rate:
condition:
"completion_acceptance_rate < 20% for 7 days"
action:
"Review .windsurfrules — AI suggestions not matching project patterns"
high_cascade_failures:
condition:
"cascade_success_rate < 50% for 3 days"
action:
"Check workspace config — .codeiumignore may be too aggressive"
credit_overspend:
condition:
"team_credits > 80% consumed before month half"
action:
"Review per-user usage, coach on credit conservation"
inactive_seats:
condition:
"user has <10 interactions in 30 days"
action:
"Offer training or downgrade to Free tier"
Step 3: Build Custom Extension for Detailed Tracking
# Weekly team productivity report templateproductivity_report:period:"Week of YYYY-MM-DD"team_size:10active_windsurf_users:8ai_metrics:total_cascade_tasks:150cascade_success_rate:"78%"completion_acceptance_rate:"32%"credits_consumed:1200productivity_proxies:commits_per_developer:12# vs baseline 8 pre-Windsurfpr_turnaround_hours:6# vs baseline 12 pre-Windsurfcode_review_comments:45# quality indicatorestimated_time_saved:per_developer_per_week:"3 hours"total_team_per_week:"24 hours"monthly_value:"$7,200"# 24hrs * 4wks * $75/hrroi_calculation:monthly_windsurf_cost:"$300"# 10 seats * $30monthly_value_generated:"$7,200"roi:"2,300%"
Step 5: Dashboard Visualization
Track these metrics over time in your preferred dashboard tool:
## Recommended Dashboard Panels1. Daily Active Users vs Total Seats (line chart)
- Shows adoption trend
- Alert when utilization drops below 70%
2. Completion Acceptance Rate (line chart, 7-day rolling avg)
- Higher = better .windsurfrules quality
- Drop = rules need updating or team needs training
3. Cascade Success Rate (bar chart, weekly)
- Tracks agentic task effectiveness
- Low rate = prompts too vague or workspace too large
4. Credits per Developer (bar chart, monthly)
- Identifies power users vs underutilizers
- Guides seat tier decisions
5. Top Workflows Used (table)
- Shows which automated workflows team uses most
- Identifies candidates for new workflows
