Weekly Report

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 1f059c400d07 · 16 Oct 2026Report an issue or request a re-scan

• Publisherhoangsonww GitHub userOwner of the repository this skill is read from
• Source folderhoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-productivity/skills/weekly-reportThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict1f059c400d07A new audit runs when the source changes
• Repository statusNot archivedLast push 4 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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…

---
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

Excerpt, first 2,380 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor
git -C Claude-Code-Agent-Monitor checkout 1f059c400d07

Works in

1. 2026-10-16
   ✓SAFE B 89 / 100

   first audit · source 1f059c400d07

Questions about Weekly Report

• github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plug — the audited source at commit 1f059c400d07 and every finding aboveObserved · 16 Oct 2026

Spotted something wrong? Report a correction · Methodology