asets-gobizit/monthly-insights

Monthly Insights Skill (Himalaya edition)

Generates the Claude Code usage report, extracts the key takeaways, pulls a Zoho inbox health snapshot, saves everything to the Obsidian vault, and emails a clean summary to Danny's Zoho work inbox via the local Himalaya CLI.

Work-only artifact. This skill MUST NOT touch the personal Gmail account. Inbox summary and send destination are both strictly zoho-danny.

Configuration (hardcoded)

• Vault path: C:\Users\dansk\Claude\Obsidian@Claude\
• Notes subfolder: Claude Tips\
• Mail account: zoho-danny ([email protected], Zoho One / USA DC)
• Sender/recipient: [email protected] → [email protected] (self-send)
• Mail transport: himalaya CLI v1.2.0 via smtppro.zoho.com:465
• Real report (preferred): C:\Users\dansk\.claude\usage-data\report.html (owned by Claude Code harness — NEVER overwrite)
• Local fallback: C:\Users\dansk\.claude\usage-data\report-local-fallback.html (written by our Python script)
• Report generator: C:\Users\dansk\.claude\skills\monthly-insights\generate_report.py (local, no API calls, fallback only)

No MCP, no OAuth, no API keys, no slash commands. Just Python + Himalaya CLI, end-to-end self-contained.

HOW TO INVOKE

User says any of:

• "monthly insights"
• "insights email"
• "email me my report"
• "monthly review"

Step 1 — Obtain the report (prefer real /insights output)

Look for the real Claude Code Insights report FIRST. When the /insights harness command is triggered (by typing it in chat, or via whatever Claude Code UI affordance the user used), the harness writes its rich, semantically analyzed HTML report to:

C:\Users\dansk\.claude\usage-data\report.html            ← REAL /insights output

Danny may also have a browser-saved backup at:

C:\Users\dansk\.claude\usage-data\Claude Code Insights.html   ← user backup, DO NOT TOUCH

The real report is dramatically higher quality than any local fallback — friction narratives, inferred satisfaction, session-type classification, response-time histograms, Claude-written CLAUDE.md rules. Prefer it whenever it exists and is ≤ 30 days old.

🚨 CRITICAL — Path safety rules

• report.html is OWNED by the Claude Code harness. This skill must NEVER write to, overwrite, or delete it. It is the real /insights output.
• Claude Code Insights.html is Danny's backup. Also NEVER touch it.
• The local fallback generator writes to report-local-fallback.html — a distinct filename that can never collide with the real report.

Decision tree

IF "report.html" exists AND file mtime is within 30 days:
    report_path = "C:\Users\dansk\.claude\usage-data\report.html"     (REAL /insights — preferred)
    source = "real /insights"
ELSE IF "Claude Code Insights.html" exists AND within 30 days:
    report_path = "C:\Users\dansk\.claude\usage-data\Claude Code Insights.html"
    source = "user-saved backup of real /insights"
ELSE:
    Run: python "C:\Users\dansk\.claude\skills\monthly-insights\generate_report.py" --days 30
    report_path = "C:\Users\dansk\.claude\usage-data\report-local-fallback.html"
    source = "local fallback (lower quality)"
    In the email footer, add a note suggesting the user run /insights manually
    for a higher-quality report next time.

The local generator ONLY ever writes to report-local-fallback.html — never to report.html or Claude Code Insights.html. Both are off-limits.

Note: Claude Code's built-in /insights slash command cannot be invoked programmatically from inside a skill (slash commands are intercepted by the harness before reaching Claude). That's why the skill reads the file on disk if it already exists, and falls back to a local generator otherwise.

Step 2 — Extract key sections

Use the Read tool on C:\Users\dansk\.claude\usage-data\report.html and pull out:

1. Top friction points — category titles plus one-sentence descriptions
2. Suggested CLAUDE.md rules — every rule from the "Suggested CLAUDE.md Additions" section
3. Features to try — each feature name, one-liner, and "Why for you" rationale

Step 3 — Zoho inbox health snapshot (work only)

Pull a quick snapshot of the work inbox. Never touch the personal Gmail account.

himalaya envelope list -a zoho-danny -p 1 -s 30

From the output, compute:

• Unread count — envelopes where the FLAGS column does NOT contain S (seen)
• Top 5 senders in the last 30 messages — group by FROM, count, sort descending
• Latest 3 subjects — top of the list

Format it as an "Inbox Health (Zoho work)" section with exactly these three subsections.

Step 4 — Save to Obsidian vault

Use the Write tool to create:

C:\Users\dansk\Claude\Obsidian@Claude\Claude Tips\Claude Insights DD-MM-YYYY.md

Date format: European (DD-MM-YYYY), e.g. Claude Insights 05-04-2026.md

Note template:

---
date: DD-MM-YYYY
tags:
  - claude-code
  - monthly-review
type: review
---

# Claude Insights DD-MM-YYYY

## Friction Points
1. **[title]** — [one-sentence description]
2. ...

## Suggested CLAUDE.md Rules
- [rule text]
- ...

## Features to Try
1. **[feature name]** — [one-liner]
   Why for you: [rationale]
2. ...

## Inbox Health (Zoho work)
- **Unread:** N messages
- **Top 5 senders (last 30):**
  1. sender — count
  2. ...
- **Latest 3 subjects:**
  1. subject
  2. ...

## Full Report
Open `C:\Users\dansk\.claude\usage-data\report.html` in your browser.

Confirm the note was created.

Step 5 — Email via Himalaya (HTML body with MANDATORY callout)

Send the full HTML report as the email body — not a plain-text summary. The HTML renders cleanly in Zoho Mail's web client and preserves all the charts, colors, and semantic sections.

MANDATORY callout at the top of every email

Every monthly email MUST have this blue callout banner injected immediately after <div class="container"> (or at the top of <body> if no container):

<div style="background:#dbeafe;border:2px solid #2563eb;border-radius:12px;padding:20px 24px;margin:0 0 24px 0;font-family:-apple-system,Segoe UI,sans-serif;">
<p style="margin:0 0 12px 0;font-size:15px;color:#1e3a8a;line-height:1.6;">
&#128073; <strong>To get a full report with real insights + ready-to-use prompt recommendations, run <code style="background:#fff;padding:2px 8px;border-radius:4px;border:1px solid #93c5fd;font-family:monospace;color:#1d4ed8;">/insights</code> in VS Code Claude (Chat only &mdash; not in the terminal).</strong>
</p>
<p style="margin:0;font-size:15px;color:#1e3a8a;line-height:1.6;">
&#128073; <strong>The generated report will appear at:</strong> <a href="file:///C:/Users/dansk/.claude/usage-data/report.html" style="color:#1d4ed8;font-family:monospace;font-size:13px;word-break:break-all;">C:\Users\dansk\.claude\usage-data\report.html</a>
</p>
</div>

Important:

• The local fallback HTML (from generate_report.py) ALREADY has this callout baked in — no injection needed when sending the fallback.
• The real /insights HTML (report.html or Claude Code Insights.html) does NOT have it — inject it at send time before piping to himalaya.
• The user backup (Claude Code Insights.html) also does NOT have it — inject at send time.

Sending (Python, to avoid heredoc escaping)

import subprocess
from pathlib import Path

CALLOUT = '''<div style="background:#dbeafe;border:2px solid #2563eb;border-radius:12px;padding:20px 24px;margin:0 0 24px 0;font-family:-apple-system,Segoe UI,sans-serif;">
<p style="margin:0 0 12px 0;font-size:15px;color:#1e3a8a;line-height:1.6;">
&#128073; <strong>To get a full report with real insights + ready-to-use prompt recommendations, run <code style="background:#fff;padding:2px 8px;border-radius:4px;border:1px solid #93c5fd;font-family:monospace;color:#1d4ed8;">/insights</code> in VS Code Claude (Chat only &mdash; not in the terminal).</strong>
</p>
<p style="margin:0;font-size:15px;color:#1e3a8a;line-height:1.6;">
&#128073; <strong>The generated report will appear at:</strong> <a href="file:///C:/Users/dansk/.claude/usage-data/report.html" style="color:#1d4ed8;font-family:monospace;font-size:13px;word-break:break-all;">C:\\Users\\dansk\\.claude\\usage-data\\report.html</a>
</p>
</div>
'''

with open(report_path, encoding="utf-8") as f:
    html = f.read()

# Inject callout only if not already present (local fallback has it baked in)
if "To get a full report with real insights" not in html:
    # Try container div first, then body
    if '<div class="container">' in html:
        html = html.replace('<div class="container">', '<div class="container">' + CALLOUT, 1)
    else:
        html = html.replace('<body>', '<body>' + CALLOUT, 1)

msg = (
    "From: [email protected]\r\n"
    "To: [email protected]\r\n"
    f"Subject: Monthly Claude Code Review {today}\r\n"
    "MIME-Version: 1.0\r\n"
    "Content-Type: text/html; charset=utf-8\r\n"
    "\r\n"
) + html

subprocess.run(
    ["himalaya", "message", "send", "-a", "zoho-danny"],
    input=msg, text=True, encoding="utf-8", check=True,
)

Confirm himalaya returns Message successfully sent!.

Step 6 — Summary

Report back to the user:

1. ✅ Report generated at C:\Users\dansk\.claude\usage-data\report.html
2. ✅ Takeaways extracted (friction points, rules, features)
3. ✅ Zoho inbox health snapshot pulled
4. ✅ Obsidian note saved: Claude Tips/Claude Insights DD-MM-YYYY.md
5. ✅ Email sent via Himalaya to [email protected]

Security rules

• Work-only: Never query, read, or send to the gmail account in this skill. Inbox summary and send both use -a zoho-danny exclusively.
• No credentials in output: Do not echo the contents of config.toml or any password back to chat.
• No git commits from this skill: It only writes to Obsidian (gitignored) and sends email.
• Never touch report.html OR Claude Code Insights.html: The first is owned by the Claude Code harness (real /insights output), the second is Danny's browser backup. The local fallback generator writes ONLY to report-local-fallback.html, and has a hard safety check that refuses to run if its output path ever collides with either protected file.

Troubleshooting

• "account not found: zoho-danny": config file is missing the block — see C:\Users\dansk\AppData\Roaming\himalaya\config.toml, confirm [accounts.zoho-danny] exists
• Auth failure: Zoho app password rotated or revoked. Generate a new one at accounts.zoho.com → Security → App Passwords and update both backend.auth.raw lines under [accounts.zoho-danny]
• Report generator fails: check Python is available; python --version should work. The script reads C:\Users\dansk\.claude\projects\**\*.jsonl — if that directory is empty, there's nothing to analyze.
• "Rectified missing text" IMAP warnings: Zoho quirk, harmless, ignore