Run any Skill in Manus with one click

$pwd:

telemetry-integration

Name: Telemetry Integration
Author: rapidaai

// Add or modify telemetry/metrics instrumentation for assistant-api and integration-api flows while preserving metric schema compatibility and audit behavior.

Run Skill in Manus

$ git log --oneline --stat

stars:652

forks:99

updated:March 23, 2026 at 05:06

File Explorer

4 files

SKILL.md

readonly

name	telemetry-integration
description	Add or modify telemetry/metrics instrumentation for assistant-api and integration-api flows while preserving metric schema compatibility and audit behavior.

Telemetry Integration Skill

Mission

Extend observability without breaking existing metric consumers, dashboards, or external audit mapping.

Inputs expected from user

Target surface: assistant pipeline, integration callers, or both.
New metric/event names and semantic definitions.
Cardinality and privacy constraints.

If user does not answer:

Reuse existing key conventions (TIME_TAKEN, STATUS, stt_latency_ms, tts_latency_ms).
Prefer additive metrics over key redefinition.

Hard boundaries

In scope:

api/integration-api/internal/caller/metrics/metrics_builder.go
provider-specific caller metrics hooks under api/integration-api/internal/caller/<provider>/
audit mapping compatibility in api/integration-api/internal/entity/external_audit.go
assistant packet event/metric emissions in touched provider flow only

Out of scope:

unrelated business logic changes not needed for instrumentation

Compatibility rules

Do not rename existing metric keys unless all readers are updated.
Emit success/failure status symmetrically.
Keep sensitive payloads out of metric values.
Ensure first-byte/first-token latency metrics are emitted once per turn.

Validation commands

go test ./api/integration-api/internal/caller/metrics/...
go test ./api/integration-api/internal/caller/<provider>/...
go test ./api/assistant-api/internal/transformer/<provider>/...
rg -n "TIME_TAKEN|STATUS|stt_latency_ms|tts_latency_ms" api
./.claude/skills/telemetry-integration/scripts/validate.sh --check-diff --provider <provider>

related-skills.json

same repository

noise-reduction-integration.md

from "rapidaai/voice-ai"

Add or modify noise-reduction providers in assistant-api with denoiser factory wiring, packet safety, and UI option compatibility.

2026-03-23652

noise-reduction-integration.md

from "rapidaai/voice-ai"

Add or modify microphone noise-reduction providers in assistant-api with denoiser factory wiring, packet safety, and option/UI compatibility.

2026-03-23652

end-of-speech-integration.md

from "rapidaai/voice-ai"

Add or modify end-of-speech integrations in assistant-api with strict separation from VAD internals. Use for transcript/audio/history-aware turn-finalization logic, provider wiring, and EOS UI config.

2026-03-23652

llm-integration.md

from "rapidaai/voice-ai"

Add or modify LLM/integration providers in integration-api with caller factory wiring, unified provider routing, streaming behavior, and metric/audit compatibility.

2026-03-23652

local-setup-and-run.md

from "rapidaai/voice-ai"

Explain and validate local setup paths for this repo with Docker and without Docker. Use when developers need exact prerequisites, startup commands, health checks, and troubleshooting steps.

2026-03-23652

stt-integration.md

from "rapidaai/voice-ai"

Add or modify speech-to-text providers in assistant-api with transport-aware ingestion (WS/SDK/HTTP), transcript packet correctness, and UI/provider wiring.

2026-03-23652

package.json

"author": "rapidaai"

"repository": "rapidaai/voice-ai"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Information Security AnalystsComputer and Mathematical Occupations15-1212L4

name	telemetry-integration
description	Add or modify telemetry/metrics instrumentation for assistant-api and integration-api flows while preserving metric schema compatibility and audit behavior.

Telemetry Integration Skill

Mission

Extend observability without breaking existing metric consumers, dashboards, or external audit mapping.

Inputs expected from user

Target surface: assistant pipeline, integration callers, or both.
New metric/event names and semantic definitions.
Cardinality and privacy constraints.

If user does not answer:

Reuse existing key conventions (TIME_TAKEN, STATUS, stt_latency_ms, tts_latency_ms).
Prefer additive metrics over key redefinition.

Hard boundaries

In scope:

api/integration-api/internal/caller/metrics/metrics_builder.go
provider-specific caller metrics hooks under api/integration-api/internal/caller/<provider>/
audit mapping compatibility in api/integration-api/internal/entity/external_audit.go
assistant packet event/metric emissions in touched provider flow only

Out of scope:

unrelated business logic changes not needed for instrumentation

Compatibility rules

Do not rename existing metric keys unless all readers are updated.
Emit success/failure status symmetrically.
Keep sensitive payloads out of metric values.
Ensure first-byte/first-token latency metrics are emitted once per turn.

Validation commands

go test ./api/integration-api/internal/caller/metrics/...
go test ./api/integration-api/internal/caller/<provider>/...
go test ./api/assistant-api/internal/transformer/<provider>/...
rg -n "TIME_TAKEN|STATUS|stt_latency_ms|tts_latency_ms" api
./.claude/skills/telemetry-integration/scripts/validate.sh --check-diff --provider <provider>

telemetry-integration

Telemetry Integration Skill

Mission

Inputs expected from user

Hard boundaries

Compatibility rules

Validation commands

More from this repository

More from this repository

Telemetry Integration Skill

Mission

Inputs expected from user

Hard boundaries

Compatibility rules

Validation commands