agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/email-digest/SKILL.md

email-digest

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Generate categorized email digest from Gmail - unread count, actionable items, newsletters. Use when user says "email digest", "check my email", or "what emails need attention".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If search_query: gmail_search(query=search_query, max_results=20)

    line 29
  2. Very specific:

    If "unauthorized" or "401": learn_tool_fix("gmail_list_emails", "unauthorized", "OAuth expired", "Re-authenticate Gmail")

    line 47

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Email Digest

Fetch and categorize recent Gmail. Requires developer persona for Gmail tools.

Inputs

InputTypeDefaultPurpose
sincestring"24"Hours back to look
labelsstring""Comma-separated labels filter
search_querystring""Optional Gmail search

Workflow

1. Load Persona

  • persona_load("developer") — Gmail tools

2. Gather Email Data

  • gmail_unread_count — total unread
  • gmail_list_labels — available labels
  • gmail_list_emails(max_results=50, hours_back=since)
  • If search_query: gmail_search(query=search_query, max_results=20)

3. Categorize

  • Parse email list: newsletters (newsletter, digest, unsubscribe, noreply), actionable (action required, urgent, approval, deadline), regular
  • Build: total, emails, newsletters, actionable, has_actionable

4. Read Actionable (if any)

  • gmail_read_email(message_id="latest") — first actionable
  • gmail_get_thread(thread_id="latest") — thread context

5. Build Digest

  • unread_count, total_emails, actionable_count, newsletter_count

6. Error Handling

  • If "unauthorized" or "401": learn_tool_fix("gmail_list_emails", "unauthorized", "OAuth expired", "Re-authenticate Gmail")

7. Post-Action

  • memory_session_log("Generated email digest", "Unread: X, Actionable: Y")

Output Format

## Email Digest (Last Xh)

**Unread:** N | **Total Recent:** M

### Actionable Items (count)

- [list]

### Regular Emails

- [list]

### Newsletters

- [list]

### Quick Actions

- gmail_read_email(message_id="<id>")
- gmail_search(query="...")

Key Details

  • OAuth: Gmail uses same OAuth as Calendar
  • Chains to: schedule_meeting, create_jira_issue
  • Provides context for: standup_summary, weekly_summary

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free