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

dau

Skill2 starsChanged 7 months agoMITView on GitHub

Daily active users for the current TelemetryDeck app. Accepts optional interval / event / compare flags as arguments.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Run the daily-active-users recipe.

    line 8
  2. Very specific:

    If the user didn't specify a window, use --interval last-30d.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

DAU

Run the daily-active-users recipe. Default window: last 30 days.

Pass any $ARGUMENTS straight through to the CLI — the user may be asking for a specific window, event filter, or period comparison:

tdq dau $ARGUMENTS

Examples of how users ask → what to run:

  • "DAU for the last week" → tdq dau --interval last-7d
  • "DAU trend this month" → tdq dau --interval this-month
  • "DAU week-over-week" → tdq dau --interval last-7d --compare prior-period
  • "DAU of App_launched last 30 days" → tdq dau --event App_launched --days 30

If the user didn't specify a window, use --interval last-30d. After the table prints, add a one-paragraph plain-English summary: peak day, trough day, trend direction, any obvious drops. Always note the opt-in-sample caveat ("Numbers reflect the opted-in cohort only").

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