Skip to main content
affpapa.org
RU EN
skill CX Codex

weekly-report — Claude Code skill for weekly reports

Turns Agent Monitor data into a weekly view of sessions, costs, tokens, tool use, and completion. Use it to review a chosen week or date range.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill weekly-report -a claude-code
Open on GitHub

What weekly-report does

The skill pulls session, analytics, and pricing data from Agent Monitor and builds a report for the selected period. Ask for the current week, the previous one, or a date range. With no period specified, it uses Monday through Sunday of the current week.

The report compares the week with the one before it and breaks activity down by day. It also covers token and cost figures, frequently used tools, tool errors, session completion, and productivity patterns, then suggests areas to address next week. Agent Monitor must respond at http://localhost:4820; the session request uses limit=200.

What it helps with

  • compare session activity with the previous week
  • review daily token volume and costs
  • identify tools with high error rates
  • measure how many sessions were completed
  • draft next-week workflow recommendations

Example prompts for the agent

  • Create a report for this week using Agent Monitor data.
  • Compare last week with the week before and break down costs by day.
  • Prepare a report for 2025-04-07 to 2025-04-13.

How to install weekly-report

1Skills CLI (Vercel)

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill weekly-report -a claude-code

2Manually: put the files in place

~/.claude/skills/weekly-report/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/weekly-report/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about weekly-report

How do I install weekly-report in Claude Code?

Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill weekly-report -a claude-code. The skill file is available at ~/.claude/skills/weekly-report/SKILL.md.

What does weekly-report do?

It turns Agent Monitor data into a weekly report covering session trends, costs, tokens, tool activity, completion, and suggested next steps.

What does weekly-report need to run?

Agent Monitor must respond at http://localhost:4820, which the skill uses to retrieve session, analytics, and pricing data.

Source text

SKILL.md · MIT 
---
name: weekly-report
description: >
  Compile a weekly productivity report using Agent Monitor data — daily_sessions
  and daily_events trends, per-session costs from pricing engine, token volumes
  (input/output/cache_read/cache_write + baselines), tool usage top 20,
  session completion rates by status, and workflow intelligence metrics.
---

# Weekly Report

Generate a comprehensive weekly productivity report from Agent Monitor data.

## Input

The user provides: **$ARGUMENTS**

This may be:
- "this week" or empty (default: current week Mon-Sun)
- "last week" for the previous week
- A date range: "2025-04-07 to 2025-04-13"

## Procedure

1. **Fetch weekly data** from `http://localhost:4820`:
   - `GET /api/sessions?limit=200` — filter to target week (default sort: most recently updated first)
   - `GET /api/analytics` — aggregated analytics
   - `GET /api/pricing/cost` — cost data

2. **Build the weekly report**:

   ### 📊 Week at a Glance
   | Metric | This Week | Last Week | Change |
   |--------|-----------|-----------|--------|
   | Sessions | N | N | ↑/↓ N% |
   | Total Hours | N | N | ↑/↓ N% |
   | Tokens Used | N | N | ↑/↓ N% |
   | Total Cost | $X.XX | $X.XX | ↑/↓ N% |
   | Completion Rate | N% | N% | ↑/↓ |

   ### 🏆 Highlights
   - Most productive day (by sessions completed)
   - Longest session and what it accomplished
   - Most used tools and any new tools adopted
   - Notable achievements (complex tasks completed, errors resolved)

   ### 📈 Daily Breakdown
   | Day | Sessions | Hours | Cost | Completion |
   |-----|----------|-------|------|------------|
   For each day of the week with activity.

   ### 🔧 Tool Usage Report
   - Top 10 tools by invocation count
   - Tools with highest error rate
   - Tool usage distribution chart (text-based)

   ### 💡 Productivity Insights
   - Peak productivity hours
   - Average session duration and trend
   - Cost efficiency trend
   - Model usage distribution

   ### 🎯 Recommendations for Next Week
   - Based on error patterns: what to improve
   - Based on cost trends: optimization opportunities
   - Based on tool usage: workflow suggestions

## Output Format

Professional report format with:
- Executive summary (3 sentences max)
- Structured tables with week-over-week comparisons
- Emoji-prefixed section headers for scannability
- Actionable recommendations in priority order

© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar skills

All skills for Notes, tasks and projects →
find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. CX Codex +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. 1,038,491installs grilling Matt Pocock Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting. 979,543installs teach Matt Pocock Turns the current directory into a learning workspace and keeps progress across sessions. Use it when learning needs to support a concrete goal in your project. 862,247installs

From the same set60

hook-failure-audit Audits hook delivery health using Agent Monitor metrics, tracking unreturned tool calls, unclosed subagents, and stalled ingestion pipelines. CX Codex +1 ★ 1,121repo stars error-scan Scans recent Claude Code sessions for API errors and unfinished tool calls, then ranks failures by tool and model. Useful when you need to see what is breaking. CX Codex +1 ★ 1,121repo stars api-error-report Turns Agent Monitor data into a report on APIError events: how many, in which sessions and models, and what likely caused them. CX Codex +1 ★ 1,121repo stars workflow-optimizer Analyzes agent DAGs, tool call transitions, and token expenses via the Agent Monitor API. Identifies retry loops, error flows, and model delegation waste. CX Codex +1 ★ 1,121repo stars time-of-day Sorts sessions and events into hour-of-day and day-of-week bins, then marks peak and low-output windows. Useful when you plan a work schedule. CX Codex +1 ★ 1,121repo stars sprint-summary Summarizes Claude Code sprint activity using Agent Monitor data: session costs, model breakdown, project groupings, and velocity metrics. CX Codex +1 ★ 1,121repo stars monthly-review Builds a monthly retrospective from Agent Monitor data, comparing sessions, costs, tokens, and project activity. Use it to review the month and plan the next one. CX Codex +1 ★ 1,121repo stars daily-standup Turns your recent Claude sessions into a standup report: work done per project, errors hit, what it cost. CX Codex +1 ★ 1,121repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor