agentleFS
Sign inStart free
agenkinagenkin/telemetrydeck-analytics/skills/query/SKILL.md

query

Skill2 starsChanged 7 months agoMITView on GitHub

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).

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use attach-db, install-duckdb and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • duckdbSkill

    attach-db

    Attach a DuckDB database file for use with /duckdb-skills:query. Explores the schema (tables, columns, row counts) and writes a SQL state file so subsequent queries can restore this session automatically via duckdb -init.

    Also in 3 projects that use this

  • carlopiSkill

    install-duckdb

    Install or update DuckDB extensions. Each argument is either a plain extension name (installs from core) or name@repo (e.g. magic@community). Pass --update to update extensions instead of installing.

    Also in 3 projects that use this

  • carlopiSkill

    read-file

    Read and explore any data file (CSV, JSON, Parquet, Avro, Excel, spatial, …) by filename only — resolves the path automatically. Uses DuckDB + the magic extension for format auto-detection. Installs magic if needed.

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 18 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 17 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run raw TQL against the current app.

    line 8
  2. Very specific:

    Before writing the JSON, read skills/analytics/tql/index.md in this plugin to route to the right sub-reference (filters, aggregators, …

    line 26
  3. Very specific:

    Every query needs queryType and granularity.

    line 30
  4. Very specific:

    Prefer userCount / thetaSketch over deprecated cardinality.

    line 31
  5. Very specific:

    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:

    line 33

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 the appID + isTestMode=false selectors yourself).
  • Every query needs queryType and granularity.
  • Prefer userCount / thetaSketch over deprecated cardinality.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free