gws

gws gmail +triage --max 1 --format json

"This skill requires the Google Workspace CLI (

gws

) to access your Gmail. You can install it and the related Gmail skills using

npx skills add nicholasgasior/gws

(or however the gws skills are distributed). Once installed, run

gws auth login

to authenticate, then try again."

gws

~/.config/email-gazette/config.json

~/.config/email-gazette/config.json

~/.config/email-gazette/

{
  "gazette_name": "The Email Gazette",
  "tagline": "All the Email That's Fit to Print",
  "output_dir": "~/Desktop/email-gazette",
  "topics": ["technology", "AI", "business"],
  "email_cap": 50,
  "date_format": "YYYY-MM-DD"
}

1. Gazette name — "What would you like to call your gazette?" (e.g., "The Morning Wire", "Alex's Daily Brief", "The Inbox Times"). This becomes the masthead title.
2. Tagline — "Want a tagline beneath the masthead?" Suggest a default like "All the Email That's Fit to Print" but let them customize (e.g., "Your inbox, editorialized", "News from the void").
3. Output directory — "Where should I save past editions?" Suggest

   ~/Desktop/email-gazette/

   as default. Create the directory if it doesn't exist.
4. Topics of interest — "What topics matter most to you? These get headline treatment." Suggest common categories (technology, AI, business, finance, crypto, health, politics, science) but let them specify anything. Everything else still appears, just in smaller print.
5. Email cap — "How many unread emails should I process per edition?" Default: 50. More = richer gazette but slower.
6. Date format for filenames — "How should I name the files?" Default:

   YYYY-MM-DD.html

   (sorts well). Alternative:

   DD-MM-YYYY.html

   .

gws gmail users messages get --params '{"userId":"me","id":"MESSAGE_ID","format":"metadata","metadataHeaders":"Subject"}' --format json

• Full read for emails matching the user's topics of interest, anything that looks like it contains important news, and personal emails that seem urgent
• Subject-only is fine for obvious marketing, automated notifications, and promotional emails

• X/Twitter posts from notable accounts discussing the topic
• arXiv papers if the story involves research or a model release
• Official blog posts from the companies involved
• News articles from reputable press

[topic] [key company/person] [current year]

• Newsletters and updates matching the user's topics of interest
• Breaking or time-sensitive information in those domains
• Major industry news

• Emails requiring urgent action
• Important deadlines or reminders
• Interview requests, scheduling, or meeting invitations
• Anything from a real person (not a mailing list) that seems urgent or important

• Routine automated notifications
• Low-value marketing newsletters
• Social media digests
• Promotional emails
• Anything that doesn't need attention

• Use a distinctive serif font for headlines (e.g., from Google Fonts: Playfair Display, Cormorant Garamond, or similar editorial serif)
• A clean readable serif or sans-serif for body text (e.g., Source Serif Pro, Libre Baskerville, or similar)
• The masthead should use the user's configured gazette name, rendered grand and prominent like a real newspaper nameplate
• Include the current date beneath the masthead, formatted like a newspaper date line (e.g., "Saturday, March 8, 2026")
• Show the user's configured tagline in italics beneath the name

• Multi-column layout using CSS grid, like a real newspaper
• HEADLINE NEWS gets the most space: a lead story spanning multiple columns at the top, with supporting stories in a grid
• CRUCIAL ALERTS get a visually distinct treatment: a bordered box with a red or bold accent, "URGENT" or "BREAKING" style banners
• IN OTHER NEWS goes at the bottom in noticeably smaller type, compressed like classified ads
• Add subtle column rules (thin vertical lines between columns) for authenticity

• Thin horizontal rules to separate sections
• A subtle paper/cream background color for warmth
• Drop caps on the lead story's first paragraph
• Section headers styled like newspaper section labels (derived from the user's topics, e.g., "TECHNOLOGY", "FINANCE", "AI & MACHINE LEARNING")
• For each article/email summary: a headline (derived from the subject), a brief summary (2-3 sentences), and the source/sender in small italics
• Stories with particularly important or newsworthy content get larger headlines and more column space

1. Email references — Each email that contributed to a story gets a superscript number (e.g.,

   <sup>[1]</sup>

   ) linking to the email in Gmail:

   https://mail.google.com/mail/u/0/#inbox/MESSAGE_ID

2. Web references — External sources from web research (Step 2b) also get superscript numbers, continuing the sequence. These link directly to the external URL.

• Visually prominent: boxed section with distinct background color or border
• Labels like "URGENT", "ACTION REQUIRED", "REMINDER" as small badges
• Key details: who it's from, what's needed, any deadline

• Very small font size, dense compact layout
• Just sender, subject, and one line of context
• Each item links to its source email
• Should feel like the fine print at the bottom of a newspaper page

• Single self-contained HTML file (all CSS inline or in a

  <style>

  block)
• Load fonts from Google Fonts CDN (the only external dependency allowed)
• Responsive: optimized for desktop but shouldn't break on mobile
• No JavaScript required unless you want subtle hover effects
• Save to

  {OUTPUT_DIR}/{DATE}.html

  using the user's configured directory and date format

• Read-only. Never modify, delete, or mark emails as read.
• Empty inbox? Generate a charming gazette page that says something like "No News is Good News" with a tasteful empty-state design.
• Group related emails. Multiple emails from the same newsletter or about the same topic should be merged into a single story.
• Editorial voice. Write summaries in a newspaper editorial voice: concise, informative, slightly formal but engaging. Transform email subjects into proper newspaper-style headlines and ledes.
• It's a newspaper, not a list. The gazette should feel like a real publication. Editorialize the presentation — the goal is to make reading email feel like reading the morning paper.