Kripu77

Telemetry — Development skill for Claude Code

Development community

Pull breakage or product-performance evidence.

How to install Telemetry

Installs to ~/.claude/skills/kripu77-software-factory-telemetry/SKILL.md

Terminal

mkdir -p ~/.claude/skills/kripu77-software-factory-telemetry && curl -fsSL https://raw.githubusercontent.com/Kripu77/software-factory/HEAD/commands/telemetry.md -o ~/.claude/skills/kripu77-software-factory-telemetry/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Telemetry does

name: telemetry description: Pull breakage or product-performance evidence. Funnels, feature completion, errors. Do not implement.

Read `lanes/telemetry.md` and `telemetry/CONTRACT.md`. Answer the question with evidence only. Name the adapter. Do not classify. Do not invent replays or funnels. Do not merge.

At start, factory.sh mem read for this issue if one was given. Write started only if none in progress: factory.sh mem write --lane telemetry --status started --harness

Alternatives in Development

Investigate Performance — Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evid 1.6k ★
Claude Private — Claude Code without any telemetry - the perfect cli to combo with CCR 350 ★
Diagnose — Diagnose errors and problems in ADVPL/TLPP code - compilation errors, runtime errors, performance issues, and 136 ★