How to Generate Shareable HTML Research Briefs with /last30days
Problem
Raw markdown research is great for developers but unreadable for non-technical stakeholders. Copying markdown into Slack loses formatting. Emailing raw text looks unprofessional. I needed a way to share research briefs that looks good, works offline, and has no dependencies.
The Solution
Add --emit=html to any /last30days query and it produces a self-contained HTML file:
/last30days OpenClaw --emit=htmlYou can also use plain language:
/last30days OpenClaw, give me a shareable HTML brief/last30days Cursor IDE for slackWhat the HTML Brief Contains
The output is a single self-contained file with:
- Badge and metadata line at the top
- Full synthesis with all citations rendered as links
- Engine footer (the “All agents reported back!” tree) for provenance
- Colophon with the topic and re-run instructions
- Data quality warnings stay in stderr logs — never leak into the shareable artifact
Technical specs:
- Inline CSS — no external dependencies
- System-font fallbacks: Inter and JetBrains Mono
- Dark mode by default
- Print-friendly layout
- Zero JavaScript — just HTML and CSS
- Works offline
Custom Location
Save to a specific directory:
/last30days Anthropic earnings --save-dir ~/client-reports --emit=htmlThe file saves alongside the raw markdown in LAST30DAYS_MEMORY_DIR (defaults to ~/Documents/Last30Days/).
Converting Existing Markdown
You can also convert any existing markdown synthesis to HTML:
/last30days --synthesis-file ~/Documents/Last30Days/topic-synthesis.mdThis is useful when you have saved briefs you want to share retroactively.
Summary
In this post, I showed how to use --emit=html to transform a raw research brief into a professional, dark-mode, self-contained HTML file. The key point is that it requires no dependencies, loses no formatting, and works offline — you can drag it into Slack, attach to email, or embed in Notion.
Final Words + More Resources
My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me
Here are also the most important links from this article along with some further resources that will help you in this scope:
Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!
Comments