agentleFS
ai-analyst-labai-analyst-lab/ai-analyst/.claude/skills/metrics/SKILL.md

metrics

Skill304 starsChanged 2 months agoMITView on GitHub

Browse, search, and display metric definitions from the active dataset's metric dictionary. This skill provides quick access to how metrics are defined, computed, and validated. Use this skill whenever the user wants to see metric definitions, understand how a metric is calculated, check what metrics are available, or verify a metric's specification before using it in analysis. Trigger on phrases like "/metrics", "show me the metrics", "what metrics do we track?", "how is [metric name] calculated?", "what's the definition of [metric]?", "list all metrics", "show me revenue metrics", "what metrics are in this dataset?", "define conversion rate", "how do we measure retention?", "what's in the metric dictionary?", "search for engagement metrics", "show me all KPIs", or any question about metric definitions, specifications, or formulas. Also use this skill during analysis when you need to confirm a metric's exact definition before computing it, or when the user references a metric name and you need to verify its calculation logic. This skill is essential for ensuring analytical consistency and preventing metric confusion across the organization.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docgen, knowledge-graph and 10 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.
  • prsolansSkill

    docgen

    Generate professional contract/agreement PDFs (and .docx CLM templates) from a declarative YAML config using the yaml-doc-generator tool ("docgen"). Use this whenever the user wants to create, manufacture, or mock up agreement documents — an MSA, NDA, SaaS/subscription agreement, amendment, exhibit, SOW, renewal notice, loan/credit agreement, fund/investment doc, BAA/DPA, government contract, or a whole document FAMILY between named parties — especially demo/test documents to load into Docusign Navigator/CLM or to feed an agreement-lifecycle agent. Triggers include "generate an MSA/NDA/agreement", "make demo contracts", "create a document family for <party> and <party>", "use docgen", or "use the yaml-doc-generator". Produces real PDFs with parties, clauses, and a manifest of critical dates (renewal/expiration).

    Also in 3 projects that use this

  • ddehartSkill

    knowledge-graph

    Search, capture, and query the claude-code-plugins knowledge graph. Use when asked to "capture this", "add this to the graph", "what do we know about X", "update the graph", "check the graph for X", or when a decision, pattern, or non-obvious fact surfaces mid-session that's worth recording. Also: "log an observation", "what patterns do we have about skill triggering", "any decisions on the knowledge-commons plugin", "what do we know about the commit-creator agent".

    Also in 3 projects that use this

  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 3 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 9 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing a metric spec, to check for existing definitions

    line 16
  2. Very specific:

    Read .knowledge/active.yaml to identify the active dataset.

    line 27
  3. Very specific:

    Read .knowledge/datasets/{active}/metrics/index.yaml for the metric list.

    line 28
  4. Distinctive:

    If no metrics directory exists: "No metric dictionary for this dataset.

    line 29
  5. Very specific:

    Read .knowledge/datasets/{active}/schema.md to explore available tables/columns

    line 38
  6. Very specific:

    Fallback search strategy: Search working/, outputs/, and .knowledge/analyses/ for recent usage of the metric name

    line 48
  7. Distinctive:

    If found in recent work, extract the formula/definition used and offer to formalize it

    line 49
  8. Distinctive:

    If not found anywhere, suggest defining it via metric-spec skill

    line 50
  9. Distinctive:

    If no matches: list available categories and suggest closest match

    line 55
  10. Distinctive:

    Search metric names and descriptions (case-insensitive substring)

    line 58
  11. Distinctive:

    Don't just say "not found" — be proactive

    line 61
  12. Very specific:

    Read .knowledge/datasets/{active}/schema.md to explore tables/columns

    line 62
  13. Distinctive:

    After displaying metrics, suggest relevant actions:

    line 69
  14. Distinctive:

    Metric referenced but not in dictionary: Search recent work for usage, extract definition if found, offer to formalize it.

    line 77

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

Skill: Metrics

Purpose

Browse, search, and display metric definitions from the active dataset's metric dictionary. Provides quick access to how metrics are defined, computed, and validated.

When to Use

  • User says /metrics or "show me the metrics" or "what metrics do we track?"
  • During analysis, to confirm a metric's definition before computing it
  • When writing a metric spec, to check for existing definitions

Invocation

/metrics — list all metrics for the active dataset /metrics {id} — show full spec for a specific metric /metrics category={cat} — filter by category (e.g., monetization) /metrics search={term} — search metric names and descriptions

Instructions

Step 1: Load Metric Dictionary

  1. Read .knowledge/active.yaml to identify the active dataset.
  2. Read .knowledge/datasets/{active}/metrics/index.yaml for the metric list.
  3. If no metrics directory exists: "No metric dictionary for this dataset. Use the metric-spec skill to define metrics."

Step 2: Execute Command

List all (/metrics):

  • Display as a table: id, name, category, direction, validation_status
  • Group by category
  • Show total count
  • If dictionary is empty AND user mentions specific analysis context (e.g., "revenue analysis", "conversion analysis"):
    • Read .knowledge/datasets/{active}/schema.md to explore available tables/columns
    • Suggest 3-5 relevant metrics the user could define for their analysis context
    • Include suggested SQL formulas for each
    • Reference the metric-spec skill for formalization

Show specific (/metrics {id}):

  • Read .knowledge/datasets/{active}/metrics/{id}.yaml
  • Display: name, category, owner, full definition (formula, unit, direction, granularity), source tables, dimensions, guardrails, typical range, validation status
  • If metric not found:
    • Suggest closest match from index (fuzzy string match on name)
    • Fallback search strategy: Search working/, outputs/, and .knowledge/analyses/ for recent usage of the metric name
    • If found in recent work, extract the formula/definition used and offer to formalize it
    • If not found anywhere, suggest defining it via metric-spec skill

Filter by category (/metrics category=monetization):

  • Filter index by category field
  • Display filtered table
  • If no matches: list available categories and suggest closest match

Search (/metrics search=revenue):

  • Search metric names and descriptions (case-insensitive substring)
  • Display matching metrics
  • If no matches found:
    • Don't just say "not found" — be proactive
    • Read .knowledge/datasets/{active}/schema.md to explore tables/columns
    • Identify columns related to the search term (e.g., "revenue" → find total_amount, revenue, sales columns)
    • Suggest 3-5 metrics the user could define based on available data
    • Include table.column references and suggested formulas
    • Offer to define the metric via metric-spec skill

Step 3: Contextual Suggestions

After displaying metrics, suggest relevant actions:

  • "Want to validate {metric} against the current data? Use the data-profiling skill."
  • "Need to define a new metric? Use the metric-spec skill."
  • "Want to see how {metric} trends over time? Ask me to analyze it."

Edge Cases

  • No active dataset: Prompt to connect one via /connect-data
  • Empty metric dictionary: Suggest using metric-spec skill. If user mentioned specific analysis context (revenue, conversion, engagement), proactively suggest relevant metrics to define.
  • Metric referenced but not in dictionary: Search recent work for usage, extract definition if found, offer to formalize it.
  • Stale validation: Flag metrics where last_validated is >30 days ago
  • Search returns no results: Explore schema and suggest metrics related to the search term rather than just reporting "not found"

Why These Guidelines Matter

The goal is to make the metrics skill helpful in all scenarios — even when the dictionary is empty or search fails. Users often ask about metrics before they're formally defined. Instead of dead-ending with "not found," we want to:

  1. Understand user context — If they mention "revenue analysis" or search for "revenue", they're signaling what domain they care about
  2. Explore available data — Read the schema to see what's actually available
  3. Suggest concrete next steps — Provide specific metric candidates with formulas, not just generic advice
  4. Lower friction for formalization — Make it easy to go from "I need this metric" to "this metric is now defined"

This approach turns the metrics skill from a simple dictionary lookup into an intelligent assistant that helps users build their metric dictionary organically.

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.