weekly-metrics-report

Generates weekly metrics reports from Postgres queries and posts them to Slack.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill weekly-metrics-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-metrics-report
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/weekly-metrics-report
Command: npx skills add https://github.com/kortix-ai/suna --skill weekly-metrics-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compiling a weekly metrics report by hand means querying the database, comparing numbers against prior weeks, and writing commentary every Monday. This Skill automates that loop: it queries the metrics tables read-only, computes week-over-week deltas against a trailing window, writes plain-language commentary on notable moves, and posts one report to a Slack channel.

Core Features & Use Cases

  • Read-only Postgres queries: Pulls this week's metrics and a trailing 4-week comparison window using SELECT-only access scoped to the metrics tables.
  • Delta and trend analysis: Flags notable moves (≥15% week-over-week change or a break from a 3+ week trend) and distinguishes them from normal noise or missing data.
  • Slack report delivery: Posts exactly one structured message per run to the configured report channel, with the week's numbers, commentary on notable moves, and notes on any data gaps.
  • Use Case: A startup team schedules a weekly cron that spawns a fresh session with read-only database access; the agent queries signups, revenue, and active users, compares them to the prior four weeks, and posts a report explaining that signups rose 22% likely due to a product launch.

Quick Start

Ask the agent to run the weekly metrics report and post this week's numbers with commentary to the report channel.

Frequently Asked Questions about weekly-metrics-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a weekly metrics report from Postgres to Slack?

Schedule a weekly cron that spawns a session with read-only Postgres access and Slack posting permission. The skill queries this week's metrics, compares them against the prior four weeks, writes commentary on notable moves, and posts one message to the configured channel.

How does the report decide which metric changes are notable?

A move is flagged notable when a metric changes 15% or more week-over-week or breaks from a trend of three or more weeks. Metrics within normal week-to-week noise are reported as numbers only, with no manufactured commentary.

Can the weekly report modify the Postgres database it reads from?

No. The database role is strictly read-only and scoped to the metrics tables, so only SELECT queries are possible. The report can never insert, update, or delete the data it reports on.

What happens when metric data is missing for a week?

Missing data is reported as an explicit gap in the closing note of the Slack message rather than being filled with a guess. If a metric definition is ambiguous, the agent queries the obvious candidate table and notes the assumption in the report.

Does the report carry state between weekly runs?

No. Each run is a fresh session with no memory of prior reports. This week's numbers and the trailing comparison window are recomputed from the current database state every time.