Schema discovery — list every event name firing for the current TelemetryDeck app with 7-day and 30-day counts side by side.
How this skill is triggered — by the user, by Claude, or both
Slash command
/telemetrydeck-analytics:eventsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the schema-discovery command:
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:
@AppStorage default-not-mirrored-to-UserDefaults.register(defaults:) bug, or release gating. Ask whether an engineering change correlates with the drop date.count_7d much higher than count_30d / 4 — new event or recent surge.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.
npx claudepluginhub agenkin/telemetrydeck-analytics --plugin telemetrydeck-analyticsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.