agentleFS
Sign inStart free
reatlatreatlat/fullstory-claude-plugin/skills/quick-stats/SKILL.md

quick-stats

Skill36 starsChanged 14 days agoMITView on GitHub

Lightning-fast answers to simple numeric questions — "how many users yesterday", "what's the conversion rate", "how many sessions today". Use when the question is a single number, no analysis needed. Skips the full general-analysis workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Add minimal context: "That's +3% vs the daily average last week" — but only if you already have the comparison data.

    line 31
  2. Distinctive:

    Don't use this skill if the question is:

    line 35
  3. Distinctive:

    If the metric already exists from a previous call in the conversation, reuse it.

    line 48
  4. Very specific:

    If the question needs validation (result is zero, looks wrong), don't use Quick Stats — upgrade to general-analysis which handles …

    line 49

≈ “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

Quick Stats

One-number answers. No analysis, no session investigation, no validation dance. Just the number, with context.

When to Use

  • "How many users yesterday?"
  • "What's the conversion rate this week?"
  • "How many sessions today?"
  • "How many rage clicks last month?"
  • "What's our error count for this week?"

Short questions that expect a single numeric answer.

Workflow

Everything is one step: build, compute, present.

fullstory:build_metric(query="page views yesterday", output_type="single_number")
fullstory:compute_metric(metric_id)

Present: "12,340 page views yesterday (Aug 3)."

Add minimal context: "That's +3% vs the daily average last week" — but only if you already have the comparison data. Don't make extra calls to get it.

When NOT to Use

Don't use this skill if the question is:

  • A comparison ("mobile vs desktop") → comparisons
  • A trend ("is it getting worse?") → general-analysis (trend metric)
  • A breakdown ("by page" or "by device") → general-analysis (top_n metric)
  • A "why" question → any of the deep-dive skills

Quick Stats is for "what's the number" — nothing more.

Guidelines

  • One metric, one compute call, one answer. No extra API calls.
  • Include the time period in the answer: "12,340 page views yesterday" not "12,340 page views."
  • Surface the metric_url so the user can verify.
  • If the metric already exists from a previous call in the conversation, reuse it. Don't rebuild.
  • If the question needs validation (result is zero, looks wrong), don't use Quick Stats — upgrade to general-analysis which handles validation.

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