Create weekly reports from Postgres metrics, comparing current figures with recent weeks. Add plain-language explanations for notable changes, flag missing data, and post one report to Slack while keeping database access read-only.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Weekly metrics reporting loop. Queries the metrics tables in Postgres read-only, compares this week against recent weeks, writes plain-language commentary on what moved and why, and posts one report to {{report_channel}}.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Metric definitions, the source tables/columns, and what counts as a notable
move live in project memory (memory/weekly-report.md if present) or
this skill's defaults below. Treat that as the source of truth for exactly
which metrics to report — no more, no less. If a definition is missing or
ambiguous, query the obvious candidate table and note the assumption in the
report rather than guessing silently.
Run each metric's query against the read-only role, scoped to the metrics tables:
-- This week's window: Monday 00:00 through now
SELECT metric_name, SUM(value) AS value
FROM metrics
WHERE recorded_at >= date_trunc('week', now())
GROUP BY metric_name;
Adapt the table/column names to what the schema actually exposes (e.g.
events, subscriptions, invoices) — the shape above is illustrative, not
literal. The connection is read-only: SELECT only, nothing else is
reachable through this role.
Pull the same metrics for a trailing window (default: the prior 4 weeks) so a single-week blip can be told apart from a trend:
SELECT date_trunc('week', recorded_at) AS week, metric_name, SUM(value) AS value
FROM metrics
WHERE recorded_at >= date_trunc('week', now()) - interval '4 weeks'
AND recorded_at < date_trunc('week', now())
GROUP BY 1, 2
ORDER BY 1;
For each metric, compute week-over-week change and the trend against the trailing average. Flag as notable:
| Signal | Criteria |
|---|---|
| Notable move | ≥15% change week-over-week, or a break from a 3+ week trend |
| Steady | Within normal week-to-week noise for that metric |
| Missing data | The query returned nothing for the current or a prior week — report the gap, don't fill it with a guess |
For every notable move, write one or two plain-language sentences: what changed, the likely driver if it's inferable from the data (a launch, a known outage, a seasonal pattern), and whether it's worth the team's attention. Steady metrics get the number with no commentary — don't manufacture a narrative for noise.
One message to {{report_channel}} per run, in this shape:
Post exactly once. This is a fresh session with nothing to diff against directly — the deltas come from the Step 3 query, not from any file state — so there is nothing else to update before finishing.
</workflow> <guardrails> - **Read-only, always.** The Postgres role can `SELECT` and nothing else — no insert, update, or delete — and it's scoped to the metrics tables. The report can never change the data it reports on. - **One output.** The Slack post to {{report_channel}} is the only thing that leaves the sandbox. No writes back to Postgres, no other messages. - **No memory between runs.** Each run is a fresh session; recompute this week's numbers and the trailing comparison from the current database state rather than assuming anything from a prior report. - **Scoped secrets.** Postgres and Slack access are brokered server-side through connectors; no raw credential is ever pasted into chat. - **Report, don't act.** Notable moves get called out with plain-language commentary; deciding what to do about them belongs to the team reading the report, not the agent. </guardrails> </skill>아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.