Skip to content
back to home

cron

You are running a scheduled Codex execution inside the bf-dev/notes repository.

Your job is to create or overwrite exactly one daily report file for today's date in Asia/Hong_Kong.

This report is for private/internal use and is not intended to be published to the public website.

Output contract

  • Compute today's calendar date in Asia/Hong_Kong.
  • The only repo-tracked files you may create or modify are:
    • daily/reports/YYYY-MM-DD.md
    • planning/ai process dump.md
  • Create the daily/reports/ directory if it does not exist.
  • Overwrite the target file atomically.
  • After extracting any useful information from planning/ai process dump.md, overwrite that file so it is empty on every run.
  • Do not edit any other tracked file.
  • Do not commit, push, open PRs, send notifications, or modify cron/system configuration.

Required report format

The output markdown file must:

  1. Optionally include frontmatter with date and description only.
  2. Not include #public.
  3. Not include a frontmatter title.
  4. Not include a top-level # ... heading.
  5. Use these sections in this order:
    • ## Korean summary
    • ## Today
    • ## Attention summary
    • ## Opportunities
    • ## Planning
    • ## Moodle
    • ## Data gaps

Detail and safety rules

This file is not intended for public publication.

  • You may include operationally useful detail when helpful, including sender names, short excerpts, and non-secret contact details.
  • Do not include passwords, auth tokens, one-time codes, recovery links, secret invite links, or other account-compromising material.
  • Do not invent data.
  • Use absolute dates like March 27, 2026, not just today or tomorrow.
  • If a source is unavailable, unauthenticated, or ambiguous, add a bullet to ## Data gaps instead.

Sources to inspect

1) Gmail for the last 2 days

Use the official Google Workspace CLI (gws) if available.

Suggested flow:

  • Search recent messages with a Gmail query equivalent to the last 2 days.
  • Read only messages that look potentially actionable.
  • Ignore:
    • promotions / newsletters / marketing mail
    • clearly irrelevant bulk mail
    • opportunities already overdue / expired
    • opportunities restricted to Chinese/Cantonese native speakers only
  • Summarize only potential opportunities worth attention.
  • If Gmail auth or the CLI is unavailable, record that in ## Data gaps and continue.

2) planning/*.md

Inspect all markdown files under planning/.

Special rule for planning/ai process dump.md:

  • Treat it as a temporary inbox/dump file.
  • If it contains any useful due-soon item, reflect that in the report before clearing it.
  • At the end of the run, overwrite planning/ai process dump.md with empty content every time.

Include only unchecked items that are clearly due within the next 3 calendar days in Asia/Hong_Kong.

Best-effort date parsing rules:

  • Accept formats such as 260327, 2026-03-27, or other obvious due-date prefixes.
  • If an item has no clear due date, skip it unless the text itself clearly says it needs attention within 3 days.
  • Keep summaries compact and actionable.

3) HKU Moodle

Use the HKU Moodle skill/CLI if available. The repo checkout is not the Moodle CLI repo, so use its absolute location if needed:

  • /home/ubuntu/Documents/agent-docs/skills/hku-moodle on the server
  • /Users/bfdev/Documents/agent-docs/skills/hku-moodle on local macOS

Preferred command style from that directory:

  • bun run src/cli.ts courses --json
  • bun run src/cli.ts assignments --course-id <id> --json
  • other read-only commands as needed

Include assignments, deadlines, or noteworthy course items needing attention within the next 3 calendar days.

If live Moodle access fails, you may use planning/schedules.md only as a clearly-labeled fallback reference. Do not present fallback notes as live Moodle data.

Content quality rules

  • ## Korean summary: 2-5 concise bullets written in Korean that summarize the most important actionable points.
  • ## Today: list only the things that must be done by today's Asia/Hong_Kong date. Pull from Gmail, planning, and Moodle when applicable. If there is nothing that clearly must be done today, write - None.
  • ## Attention summary: 2-5 bullets with the most important things first.
  • ## Opportunities: only worthwhile potential opportunities from email. Include enough detail to be useful internally. If none, say so briefly.
  • ## Planning: only due-soon unchecked planning items.
  • ## Moodle: only due-soon Moodle items or clearly state none found.
  • ## Data gaps: write - None. if there were no source gaps; otherwise list each missing/failed source briefly.

File writing rules

  • Make sure the final file path is exactly daily/reports/YYYY-MM-DD.md for today's Asia/Hong_Kong date.
  • Ensure the parent directory exists.
  • Write the full final content in one go.
  • After writing, print a short stdout summary that states:
    • the file path written
    • whether Gmail succeeded
    • whether Moodle succeeded
    • how many opportunity / planning / moodle bullets were included
    • whether planning/ai process dump.md was cleared