Query
Run an arbitrary TQL query against the current TelemetryDeck app. Use when no recipe fits and a hand-written TQL is required (funnel, retention, multi-dim groupBy, postAggregations, filtered aggregations).From its SKILL.md
npx -y skills add agenkin/telemetrydeck-analytics --skill queryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things 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.
- runs commandsInstructs the agent to run 3 commands, including `tdq query -` and 2 more.
SKILL.md
1.4 KB, 305 tokens by cl100k_base, as published. Nobody here has run it
Query
Run raw TQL against the current app. Two ways:
(a) Inline JSON from $ARGUMENTS — pipe it to tdq query -:
echo '$ARGUMENTS' | tdq query -
(b) JSON file path — pass the path directly:
tdq query $ARGUMENTS
Pick (b) if $ARGUMENTS looks like a file path, else (a).
Writing the TQL
Before writing the JSON, read skills/analytics/tql/index.md in this plugin to route to the right sub-reference (filters, aggregators, intervals, funnel, retention, recipes, etc.). Do not try to recall TQL syntax from memory — the progressive-disclosure tree is there for a reason.
Rules that always apply:
- Set
"filter": { "__auto_app_and_test_mode_filter__": true }unless you need a custom filter (in which case include theappID+isTestMode=falseselectors yourself). - Every query needs
queryTypeandgranularity. - Prefer
userCount/thetaSketchover deprecatedcardinality.
If the user's first query returns (no rows), re-run with --raw to see whether the result is genuinely empty or the parser dropped it:
tdq query /tmp/q.json --raw 2>/tmp/raw.json
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.