hourly
npx machina-cli add skill cyrus-cai/claude-cobrain/hourly --openclawhourly
Display today's hourly activity reports generated automatically by the daemon.
Steps
- Resolve output directory (direct python mode):
OUTPUT_DIR="${OUTPUT_DIR:-$HOME/.claude/cobrain}"
echo "$OUTPUT_DIR"
- Build today's hourly file path and check existence:
OUTPUT_DIR="${OUTPUT_DIR:-$HOME/.claude/cobrain}"
HOURLY_FILE="$OUTPUT_DIR/$(date +%Y%m%d)-hourly.md"
test -f "$HOURLY_FILE" && echo "exists" || echo "missing"
-
If the file does not exist or is empty, report:
- "No hourly reports generated yet today. Reports are created automatically at each hour boundary when the daemon is running."
- Stop here.
-
Read and display the full contents of the hourly file using the
Readtool. -
Present the content as-is — these are pre-generated summaries, no further analysis needed.
Source
git clone https://github.com/cyrus-cai/claude-cobrain/blob/main/plugin/skills/hourly/SKILL.mdView on GitHub Overview
Displays auto-generated hourly activity reports for the current day. The daemon creates these reports at each hour boundary and stores them as a daily markdown file named YYYYMMDD-hourly.md in the output directory, which defaults to ~/.claude/cobrain.
How This Skill Works
The skill resolves OUTPUT_DIR (defaulting to ${HOME}/.claude/cobrain), builds HOURLY_FILE as $OUTPUT_DIR/$(date +%Y%m%d)-hourly.md, and checks if the file exists. If the file is missing or empty, it outputs the no-reports message; otherwise it reads and displays the full contents using the Read tool, presenting the pre-generated summaries as-is.
When to Use It
- When you need to verify today's hourly activity across the day for debugging.
- When diagnosing missing hourly reports generated by the daemon.
- When sharing a snapshot of hourly activity with teammates.
- When validating the file path and naming convention for hourly reports.
- When auditing the content of the pre-generated hourly summaries.
Quick Start
- Step 1: Ensure OUTPUT_DIR is set or rely on the default (~/.claude/cobrain).
- Step 2: Locate today’s hourly file by building HOURLY_FILE with the current date.
- Step 3: If the file exists, read and display it with the Read tool; otherwise you’ll see the no-report message.
Best Practices
- Set OUTPUT_DIR to a known path or rely on the default to ensure the file is found.
- Check for file existence before attempting to read.
- Use the Read tool to display content without modification.
- Be aware the hourly file is named YYYYMMDD-hourly.md.
- If none exists for today, report the placeholder message and stop.
Example Use Cases
- A developer checks 2pm hourly.md to verify uptime logging for today.
- An operator confirms that today's hourly.md exists and opens it for the stand-up.
- Product manager shares the 9am-5pm hourly report with stakeholders.
- Support team validates hourly.md after a daemon restart to ensure continuity.
- QA runs a quick check to ensure hourly reporting occurs on schedule.
