本文へ移動
cccskills
無料GitHub で公開

weekly-report

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.4 KB
  • agents/openai.yaml263 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

    MetricThis WeekLast WeekChange
    SessionsNN↑/↓ N%
    Total HoursNN↑/↓ N%
    Tokens UsedNN↑/↓ N%
    Total Cost$X.XX$X.XX↑/↓ N%
    Completion RateN%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

    DaySessionsHoursCostCompletion
    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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets.

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

Produce a detailed report on APIError events from Agent Monitor data — counts over time, which sessions and models are affected, and the likely root cause (rate limits, overload/529, or context-window pressure) inferred from each event's summary and data payload. Use when API errors spike or when you need to explain why requests are failing.

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

benchmark

無料

Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a spend limit or wiring up a budget guardrail.

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (total_cache_read / (total_cache_read + total_input)), cache_write vs cache_read reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session detail from /api/sessions, and dollar splits from /api/pricing/cost. Use when diagnosing cache spend or deciding whether prompt caching is paying off.

日本語の概要は準備中です。原文の説明を表示しています。

hoangsonww/Claude-Code-Agent-Monitor1,0692026年10月12日 更新

hoangsonww のスキルをすべて見る

このスキルの問題を報告する