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

report

Skill2 starsChanged 7 months agoMITView on GitHub

Generate a short markdown analytics report answering a specific product question. Pass the question as arguments.

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use opportunities, export and 9 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.
  • ansvisorSkill

    opportunities

    Finds content gaps, prompts worth tracking, and the off-site sources AI cites instead of the brand.

    Also in 3 projects that use this

  • soilmassSkill

    export

    Animation export configurations including format selection, resolution, framerate, quality, and optimization settings. Use when rendering animations for web, mobile, video, or social media. Provides tokens for all export parameters across Lottie, GIF, video, and sprite sheet formats.

    Also in 4 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 7 projects that use this

  • tokyubevoxelverseSkill

    checkup

    Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write a compact markdown analytics report that answers the user's question in $ARGUMENTS.

    line 8
  2. Distinctive:

    Always include the opt-in-cohort caveat.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 68 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

Report

Write a compact markdown analytics report that answers the user's question in $ARGUMENTS. This skill is the high-level wrapper: pick the right sub-query (recipe or raw TQL), run it, and turn the numbers into a narrative.

Process

  1. Parse the question in $ARGUMENTS. Identify: metric (count vs. users), dimension (if any), window, comparison target.
  2. Pick the command:
    • DAU/MAU trend → tdq dau / tdq mau
    • Breakdown by one dimension → tdq groupby <dim>
    • Which events fire → tdq events
    • Funnel / retention / multi-dim groupby / derived metric → write raw TQL and run via tdq query - (consult skills/analytics/tql/index.md for syntax).
  3. Run it — use the Bash tool. Capture the table output.
  4. Write the report using this structure:
## <question restated as a header>

**Top-line:** <one sentence with the key number and window>

**Method:** `<the exact `tdq …` invocation you ran>`

**Result:**
<markdown table — paste the CLI output directly>

**Interpretation:** <1–3 sentences: what the numbers mean, any trend or outlier, compared-to-what>

**Caveats:** Opt-in cohort only (TelemetryDeck samples self-selected users). <add channel skew / partial-period / small-sample notes if applicable>
  1. Where to save: inline in the conversation by default. If the user asks for a file, ask them where to save it; write to the absolute path they give. Suggest ~/Documents/TelemetryDeck/YYYY-MM-DD-<slug>.md. Never create new top-level folders in the current working directory.

Defaults

  • Window: last 30 days unless the question implies otherwise.
  • Format: table (markdown-ready).
  • Always include the opt-in-cohort caveat.
  • For "trending" / "growing" / "vs. last period" phrasings, add --compare prior-period.

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