email-digest
Skill0 starsChanged 45 days agoMITView on GitHub
Process the kSuite (Infomaniak) inbox to identify high-risk emails, analyze sentiment and urgency, recommend actions, prepare draft replies in kSuite Mail, and optionally post an executive briefing to kChat. Run with /email-digest or ask to process emails.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- chendaniely/skillstheir own version, first seen Nov 11, 2026
- dmzoneill/skillstheir own version, first seen Oct 24, 2026
- QuixiAI/Hexistheir own version, first seen Oct 8, 2026
- QuixiAI/agi-memorytheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- dmzoneill/skills★ 2same name
- chendaniely/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analystSkill
- build-appSkill
- build-websiteSkill
- business-setupSkill
- content-pipelineSkill
- content-writerSkill
- email-assistantSkill
- ksuite-setupSkill
- meeting-prepSkill
- memorySkill
- odooSkill
- plugin-builderSkill
- qfieldcloudSkill
- qgisSkill
- quarto-slidesSkill
- research-leadSkill
- researchSkill
- r-sessionSkill
- schedulerSkill
- scrum-masterSkill
- skill-creatorSkill
- task-managerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
If mcp__ksuite-mail__* tools are available you may use them instead of step 1.
- Very specific: line 23
If nothing is configured, say so in one line and offer either ksuite-setup or the manual email-assistant skill (the user pastes emails).
- Very specific: line 36
Read .tmp/email-digest/emails.json, context/my-voice.md and context/my-business.md.
- Very specific: line 50
Write the result to .tmp/email-digest/analysis.json.
- Very specific: line 54
Write .tmp/email-digest/briefing.md (Markdown, language from config/preferences.yaml):
- Very specific: line 75
Write .tmp/email-digest/drafts.json as a list of {"to", "subject", "body", "in_reply_to"} (use the original message_id for in_reply_to, …
- Very specific: line 87
Use the scheduler skill (Claude Code /schedule), for example every weekday at 7:00: "run /email-digest and post the briefing to kChat".
- Distinctive: line 92
No urgent email: still produce the briefing with counts.
“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.
Files
Email Digest (kSuite)
Inbox processing: fetch (script) -> analyze (you) -> brief (kChat or chat) -> drafts (kSuite Mail).
The analysis is done by you, inside the Claude Code session: no OpenAI key, no email content leaves the machine except to Infomaniak (where it already lives).
Prerequisites
KSUITE_MAIL_USERandKSUITE_MAIL_PASSWORDin.env(seeksuite-setup).- Optional:
KCHAT_WEBHOOK_URLfor the kChat briefing. - If
mcp__ksuite-mail__*tools are available you may use them instead of step 1.
If nothing is configured, say so in one line and offer either ksuite-setup or the
manual email-assistant skill (the user pastes emails).
Step 1: Fetch
python3 .claude/skills/ksuite-setup/scripts/mail_fetch.py --hours 24 --output .tmp/email-digest/emails.jsonOptions: --hours N, --unread-only, --folder INBOX, --limit 100. Read-only.
Step 2: Analyze (you)
Read .tmp/email-digest/emails.json, context/my-voice.md and context/my-business.md.
For each email produce:
- category: urgent / respond / delegate / archive / irate
- sentiment: positive / neutral / negative / irate
- urgency: high / medium / low
- summary: one sentence
- recommendation: what to do and why
- draft: reply text, only for urgent / respond / irate
Irate client: highest priority, de-escalation draft, recommend a same-day personal follow-up, note it in today's log. Flag anything about money, contracts or legal matters. Summarize long threads once instead of message by message.
Write the result to .tmp/email-digest/analysis.json.
Step 3: Briefing
Write .tmp/email-digest/briefing.md (Markdown, language from config/preferences.yaml):
### Synthèse mails, [date]
**🔴 Urgent (2)**
- [Expéditeur], [Objet]: [recommandation]
**🟡 À répondre (5)**
- [Expéditeur], [Objet]: [résumé]
**🟢 Faible priorité (12)**
- [n] archivables, [n] newslettersShow it in the chat. Post it to kChat only if the user confirms (or asked for it explicitly in a scheduled run):
python3 .claude/skills/ksuite-setup/scripts/kchat_post.py --file .tmp/email-digest/briefing.mdStep 4: Drafts (optional, after confirmation)
Write .tmp/email-digest/drafts.json as a list of
{"to", "subject", "body", "in_reply_to"} (use the original message_id for
in_reply_to, prefix subjects with "Re: "), then:
python3 .claude/skills/ksuite-setup/scripts/mail_draft.py --from-json .tmp/email-digest/drafts.jsonDrafts appear in kSuite Mail > Drafts. Nothing is ever sent by AIGORA.
Automation
Use the scheduler skill (Claude Code /schedule), for example every weekday
at 7:00: "run /email-digest and post the briefing to kChat".
Edge cases
- No urgent email: still produce the briefing with counts.
- IMAP login fails: the mailbox needs an application password, not the account password.
- Very large inbox: lower
--hoursor use--unread-only.
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
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.

