How do I install the Dstack Metric Brief skill?

Run npx skillmds@latest add upsolve-labs/dstack-metric-brief in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dstack Metric Brief safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dstack Metric Brief?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dstack Metric Brief free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Dstack Metric Brief?

Upsolve-Labs (@upsolve-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dstack Metric Brief by upsolve-labs

Name: Dstack Metric Brief
Author: Upsolve-Labs

Dstack Metric Brief

KPI deep dive report. Given a metric name, produces a structured brief: current value, WoW and MoM trend, top contributing segments, and notable outliers. Outputs a shareable summary for Slack, docs, or stakeholder updates. Trigger phrases: "summarize this metric", "metric brief", "what's happening with X", "give me a KPI summary", "how is [metric] doing?", "weekly metric update".

Upsolve-Labs 17268ba 2.6 KB Updated Sep 17, 2026

File contents

Update Check (run first)

_UPD=$(~/.claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || .claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true

If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/data-stack/skills/dstack-upgrade/SKILL.md and follow the "Inline upgrade flow". If JUST_UPGRADED <from> <to>: tell user "Running data-stack v{to} (just updated!)" and continue.

/metric-brief

You are producing a shareable KPI brief for a specific metric.

Before Starting

If the user hasn't specified a metric, AskUserQuestion: "Which metric do you want a brief for? (e.g. 'daily active users', 'revenue', 'conversion rate')"

Phase 1: Current Value & Trend

Open an Upsolve thread:

analyze_data("Show me <metric> for: the most recent full period, WoW change, MoM change, and the 30-day daily trend.")

Phase 2: Segment Breakdown

analyze_data("Break down <metric> by the top 3 most impactful dimensions. For each segment show the current value and WoW change.", thread_id=<id>)

Phase 3: Outliers & Notable Events

analyze_data("In the last 30 days of <metric> data, flag any single-day spikes, drops, or unusual patterns worth calling out.", thread_id=<id>)

Phase 4: Output Brief

Format for easy copy-paste into Slack or a doc:

METRIC BRIEF: <Metric Name>
As of <date>
────────────────────────────────────────
Current:   <value>
WoW:       <+/- X%>
MoM:       <+/- X%>
Trend:     <upward / downward / flat>

TOP SEGMENTS:
  <segment 1>:  <value>  (<+/- X%> WoW)
  <segment 2>:  <value>  (<+/- X%> WoW)
  <segment 3>:  <value>  (<+/- X%> WoW)

NOTABLE:
  <any spikes, drops, or anomalies worth flagging — or "Nothing unusual">

SUMMARY:
  <2–3 sentence plain-language interpretation>

Rules

Keep the brief scannable. Never include raw SQL or query details in the output.
If the metric has a known target, include % to target if the user mentions it.
Always include WoW — it's the most actionable trend signal.
If data is incomplete, note it explicitly rather than extrapolating.

---name: dstack-metric-briefdescription: KPI deep dive report. Given a metric name, produces a structured brief: current value, WoW and MoM trend, top contributing segments, and notable outliers. Outputs a shareable summary for Slack, docs, or stakeholder updates. Trigger phrases: "summarize this metric", "metric brief", "what's happening with X", "give me a KPI summary", "how is [metric] doing?", "weekly metric update".license: MIT---## Update Check (run first)```bash_UPD=$(~/.claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || .claude/skills/data-stack/bin/data-stack-update-check 2>/dev/null || true)[ -n "$_UPD" ] && echo "$_UPD" || true```If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/data-stack/skills/dstack-upgrade/SKILL.md` and follow the "Inline upgrade flow". If `JUST_UPGRADED <from> <to>`: tell user "Running data-stack v{to} (just updated!)" and continue.# /metric-briefYou are producing a shareable KPI brief for a specific metric.## Before StartingIf the user hasn't specified a metric, AskUserQuestion: "Which metric do you want a brief for? (e.g. 'daily active users', 'revenue', 'conversion rate')"## Phase 1: Current Value & TrendOpen an Upsolve thread:```analyze_data("Show me <metric> for: the most recent full period, WoW change, MoM change, and the 30-day daily trend.")```## Phase 2: Segment Breakdown```analyze_data("Break down <metric> by the top 3 most impactful dimensions. For each segment show the current value and WoW change.", thread_id=<id>)```## Phase 3: Outliers & Notable Events```analyze_data("In the last 30 days of <metric> data, flag any single-day spikes, drops, or unusual patterns worth calling out.", thread_id=<id>)```## Phase 4: Output BriefFormat for easy copy-paste into Slack or a doc:```METRIC BRIEF: <Metric Name>As of <date>────────────────────────────────────────Current: <value>WoW: <+/- X%>MoM: <+/- X%>Trend: <upward / downward / flat>TOP SEGMENTS: <segment 1>: <value> (<+/- X%> WoW) <segment 2>: <value> (<+/- X%> WoW) <segment 3>: <value> (<+/- X%> WoW)NOTABLE: <any spikes, drops, or anomalies worth flagging — or "Nothing unusual">SUMMARY: <2–3 sentence plain-language interpretation>```## Rules- Keep the brief scannable. Never include raw SQL or query details in the output.- If the metric has a known target, include % to target if the user mentions it.- Always include WoW — it's the most actionable trend signal.- If data is incomplete, note it explicitly rather than extrapolating.

Frequently asked questions