telemetry
Parent skill that routes between telemetry-pr-insights (PR/CI) and telemetry-insights (interactive analysis).
When & Why to Use This Skill
The Telemetry Parent Skill is an intelligent orchestration layer designed to route telemetry and performance queries to specialized sub-skills based on the user's context. It seamlessly bridges the gap between automated CI/CD reporting and interactive developer productivity analysis, ensuring that users receive the most relevant data-driven insights whether they are reviewing code in a PR or evaluating long-term workflow efficiency.
Use Cases
- Automated PR Insights: Automatically routing to telemetry-pr-insights during code reviews to provide branch-scoped performance data and CI bot reports.
- Developer Productivity Analysis: Handling interactive user questions like 'How efficient was I this week?' by routing to telemetry-insights with a 7-day session scope.
- Context-Aware Telemetry: Distinguishing between automated system environments (PR/CI) and manual user queries to apply the correct analysis logic without manual tool selection.
- Deep-Dive Troubleshooting: Starting with a high-level PR overview and transitioning into a deep-dive interactive session to analyze specific usage or productivity bottlenecks.
| name | telemetry |
|---|---|
| description | Parent skill that routes between telemetry-pr-insights (PR/CI) and telemetry-insights (interactive analysis). |
Telemetry Parent Skill
Routes to the appropriate telemetry sub-skill based on context.
Sub-Skills
| Skill | When to Use |
|---|---|
telemetry-pr-insights |
PR reviews, CI bots, automated reports |
telemetry-insights |
User questions about efficiency, usage, productivity |
Routing Logic
If PR/CI context:
→ telemetry-pr-insights
Else if user asks about telemetry/usage/productivity:
→ telemetry-insights
Else:
→ don't run telemetry
Examples
PR bot: Use telemetry-pr-insights with branch-scoped window.
"How efficient am I?": Use telemetry-insights with current-session scope.
"How efficient was I this week?": Use telemetry-insights with 7-day scope.
Follow-up in PR: Start with telemetry-pr-insights, switch to telemetry-insights for deeper analysis.