time-of-day
Discover when you are most active and most productive with Claude Code by bucketing sessions and events into hour-of-day and day-of-week bins from their timestamps, then flagging peak versus low-output windows. Uses the session list, per-session events, and analytics daily trends. Use when planning a schedule or deciding when to do deep work versus lighter tasks.
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill time-of-day --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Time of Day Profile activity and productivity across the hours of the day and days of the week. ## Input The user provides: **$ARGUMENTS** This may be: - empty or "all" (default: all available sessions) - a window like "last 30 days" or "last 90 days" to limit the analysis - a project path to scope the analysis to one `cwd` ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions?limit=500` | Sessions with `started_at`, `ended_at`, `status`, `cwd`, `cost`, and `metadata` (turn_count, total_turn_duration_ms) — primary source for hour/weekday bucketing | | `GET /api/events?session_id=X` | Events with `timestamp` and `event_type` (PreToolUse, PostToolUse, Stop, Compaction, APIError, etc.) — finer-grained activity within sessions and error timing | | `GET /api/analytics` | `daily_sessions` / `daily_events` (365d) and `sessions_by_status` for trend context and completion baselines | ## Report Sections ### 1. Activity by Hour of Day Bucket sessions (by `started_at`) and events (by `timestamp`) into 24 hourly bins. Show a text bar chart of session and event counts per hour. Identify the busiest hours by raw volume. ### 2. Productivity by Hour of Day For each ho
- Input
- Data Sources
- Report Sections
- 1. Activity by Hour of Day
- 2. Productivity by Hour of Day
- 3. Day-of-Week Pattern
- 4. Peak vs. Low-Output Windows
- 5. Schedule Recommendation
- Output
What does the time-of-day skill do?
Discover when you are most active and most productive with Claude Code by bucketing sessions and events into hour-of-day and day-of-week bins from their timestamps, then flagging peak versus low-output windows. Uses the session list, per-session events, and analytics daily trends. Use when planning a schedule or deciding when to do deep work versus lighter tasks.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill time-of-day --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.