DevRel metrics, analytics dashboards, and program reporting
Generates DevRel analytics reports with metrics across community, content, and events. Use when you need to create pulse, monthly, quarterly, or annual reports with visualizations and data-driven insights.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/metrics-dashboard.yamlreferences/METRICS_GUIDE.mdscripts/devrel_metrics.pyMeasure program impact with data-driven metrics and reporting.
parameters:
required:
- report_type: enum[pulse, monthly, quarterly, annual]
- metrics_focus: array[string]
optional:
- date_range: object{start, end}
- comparison_period: enum[wow, mom, yoy]
output:
report:
summary: object
visualizations: array[Chart]
insights: array[string]
recommendations: array[Action]
| Stage | Metrics |
|---|---|
| Awareness | Impressions, reach, brand mentions |
| Acquisition | Signups, registrations, first visits |
| Activation | First API call, tutorial completion |
| Retention | MAU, DAU, repeat usage |
| Revenue | Conversions, upgrades, pipeline |
| Referral | NPS, word-of-mouth, shares |
| Product | Feature adoption, feedback quality |
growth:
- total_members
- new_members_per_week
- member_retention_30d
engagement:
- daily_active_users
- messages_per_day
- questions_answered
- response_time_avg
reach:
- page_views
- unique_visitors
- social_impressions
engagement:
- time_on_page
- scroll_depth
- shares_and_saves
conversion:
- cta_clicks
- signups_from_content
- doc_to_api_calls
attendance:
- registrations
- show_up_rate
- session_attendance
satisfaction:
- nps_score
- session_ratings
- feedback_sentiment
business:
- leads_generated
- pipeline_influenced
Executive Dashboard
├── North Star Metric (primary KPI)
├── Funnel Overview
├── Weekly Trends
└── Key Highlights
Detailed Dashboards
├── Community Health
├── Content Performance
├── Event Analysis
└── Developer Journey
| Report | Frequency | Audience |
|---|---|---|
| Weekly pulse | Weekly | DevRel team |
| Monthly review | Monthly | Leadership |
| Quarterly OKR | Quarterly | Executives |
| Annual summary | Yearly | Company-wide |
Common issues:
Solutions:
retry_patterns:
data_incomplete:
strategy: "Extend collection window"
fallback: "Use available data with disclaimer"
dashboard_error:
strategy: "Refresh data sources"
fallback: "Manual data pull"
metric_anomaly:
strategy: "Verify data integrity"
fallback: "Flag for review"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Missing data | Gaps in metrics | Backfill or document |
| Wrong calculations | Audit reveals errors | Fix formula, rerun |
| Outdated dashboard | Stale data shown | Refresh pipeline |
□ Data sources connected?
□ Date ranges correct?
□ Calculations verified?
□ Comparison periods aligned?
□ Visualizations rendering?
□ Insights actionable?
test_analytics_reporting:
unit_tests:
- test_data_accuracy:
assert: "Matches source systems"
- test_calculations:
assert: "Formulas correct"
integration_tests:
- test_dashboard_load:
assert: "<5s load time"
metrics:
- reports_generated: integer
- dashboard_views: integer
- data_freshness: duration
- insight_accuracy: float
See assets/ for dashboard templates.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.