Events
TelemetryDeck product analytics for Claude Code — CLI + slash commands + progressive-disclosure TQL docs.
npx -y skills add agenkin/telemetrydeck-analytics --skill eventsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Schema discovery — list every event name firing for the current TelemetryDeck app with 7-day and 30-day counts side by side.
SKILL.md
1.0 KB, as published. Nobody here has run it
Events
Run the schema-discovery command:
tdq events $ARGUMENTS
Defaults to the top 100 events per window. The user can pass --top N to widen.
After the table prints, call out:
- Events present in 30d but absent from 7d — they stopped firing in the last week. Classic causes: feature was removed,
@AppStoragedefault-not-mirrored-to-UserDefaults.register(defaults:)bug, or release gating. Ask whether an engineering change correlates with the drop date. - Events with
count_7dmuch higher thancount_30d / 4— new event or recent surge. - Suspiciously low counts on events you expected to be frequent — may indicate a signal-ingestion regression.
If the user is hunting a specific event ("is Transcription_completed firing?"), grep/filter the table output for the name and report presence/absence explicitly.