telemetry

Route telemetry queries to the appropriate analysis sub-skill by context.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill telemetry-blueplane-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry
Source: https://github.com/blueplane-ai/bp-telemetry-core/tree/main/.claude/skills/telemetry
Command: npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill telemetry-blueplane-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes routing decisions so telemetry requests are handled by the analysis mode that matches their context, preventing PR/CI automation from triggering interactive deep-dive workflows and vice versa.

Core Features & Use Cases

  • Contextual Routing: Detects whether input originates from PR/CI automation or an interactive user and selects the matching sub-skill.
  • Scope Preservation: Forwards scope parameters such as branch, session, and time window to the chosen sub-skill to ensure accurate, scoped analysis.
  • Use Case: A PR bot can request branch-scoped summaries using telemetry-pr-insights while a developer asking about productivity receives session or 7-day analysis via telemetry-insights.

Quick Start

Use the telemetry skill to route a PR context to telemetry-pr-insights for a branch-scoped report.

Frequently Asked Questions about telemetry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route telemetry queries to the correct analysis context in CI automation?

Telemetry routing detects whether input originates from CI automation or an interactive user, then forwards scope parameters like branch and time window to the matching analysis sub-skill.

Can I get branch-scoped telemetry insights automatically during a PR code review?

Yes, within PR review bots this skill detects the PR context and routes branch-scoped parameters to specialized sub-skills to generate targeted pull request telemetry reports.

What is the best way to prevent CI automation from triggering interactive telemetry deep-dives?

Centralizing telemetry routing decisions separates CI automation from interactive user sessions, ensuring context-specific analysis modes handle their respective telemetry requests without overlap.

Does telemetry routing preserve session and time window scope when forwarding analytics requests?

Yes, telemetry routing preserves scope parameters such as branch, session, and time window, forwarding them to the chosen sub-skill to ensure accurate and scoped analytics output.

How do I set up telemetry routing for both interactive developer productivity and automated CI workflows?

Use this skill to route interactive developer requests to session-based analysis sub-skills while directing CI automation contexts to branch-scoped telemetry insights automatically.

Why does my telemetry request return the wrong analysis scope for my current git branch?

Without centralized telemetry routing, requests lack proper context detection and scope parameter preservation, causing mismatched analysis sub-skills to handle branch-scoped or session-scoped queries incorrectly.