Time Of Day logo

Time Of Day

CommunityPopular
hoangsonww
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.

Overview

Publisherhoangsonww
RepositoryClaude-Code-Agent-Monitor
Skill nametime-of-day
Stars
1.1K
Forks
260
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hoangsonww on GitHub. Read the source before you install it.

Installation

Install the Time Of Day AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-productivity/skills/time-of-day
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/Claude-Code-Agent-Monitor
mkdir -p .claude/skills
cp -r /tmp/Claude-Code-Agent-Monitor/plugins/ccam-productivity/skills/time-of-day .claude/skills/time-of-day
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Time Of Day in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Time Of Day on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Time Of Day is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

EndpointReturns
GET /api/sessions?limit=500Sessions 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=XEvents with timestamp and event_type (PreToolUse, PostToolUse, Stop, Compaction, APIError, etc.) — finer-grained activity within sessions and error timing
GET /api/analyticsdaily_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 hour bin, compute completion rate (completed / total sessions started in that hour) and average sustained turn time (total_turn_duration_ms / turn_count, ms → minutes). Distinguish "active" hours (high volume) from "productive" hours (high completion + sustained turns).

3. Day-of-Week Pattern

Bucket the same metrics into 7 weekday bins. Table: weekday, sessions, completion rate, avg cost, dominant model.

4. Peak vs. Low-Output Windows

  • Peak windows: hours/days with high completion rate and long sustained turns.
  • Low-output windows: hours/days with high abandonment/error/Compaction rates or fragmented short turns. Pull error timing from /api/events event types (APIError, Compaction) to corroborate.

5. Schedule Recommendation

Suggest which hour/weekday blocks to reserve for deep work and which to use for lighter or shallower tasks, grounded in the buckets above.

Output

  • Markdown with text-based bar charts (e.g., 09:00 ████████ 24) for the hourly and weekday distributions.
  • Tables for the hour and weekday metrics; ▲ / ▼ for above/below the overall mean.
  • Currency in USD to 4 decimals; durations in minutes (convert from ms).
  • Cite only numbers from the API. State how many sessions/events were bucketed and exclude sessions missing started_at or the focus metadata, noting the count.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Time Of Day AI 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.

Why use Time Of Day on TypingMind?

Because you install it once and use it with any model. Time Of Day is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Time Of Day in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-productivity/skills/time-of-day. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Time Of Day?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Time Of Day?

As many as you like. As long as a model supports skills, you can use Time Of Day with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Time Of Day AI skill free?

Yes. It is published on GitHub by hoangsonww under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇