comms

Name: comms
Availability: InStock
Author: chowderr

Convert client email and Slack history into weekly Obsidian digests with thread summaries.

2|1|Updated Feb 14, 2026

Search Tags:#summarization #email #client management #obsidian #slack #comms #weekly digests

Ready to run

npx skills add https://github.com/hamchowderr/braynee --skill comms-hamchowderr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comms
Source: https://github.com/hamchowderr/braynee/tree/main/skills/comms
Command: npx skills add https://github.com/hamchowderr/braynee --skill comms-hamchowderr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, python3, slk, claude, obsidian eval, protonmail-cli, and includes scripts (resource) components.

What problem does it solve?

It eliminates the manual effort of collecting scattered email and Slack history and turning it into readable, structured weekly summaries per client inside your Obsidian PARA-style vault.

Core Features & Use Cases

Weekly rollups per client: Summarises email + Slack conversations into one weekly rollup file for each client.
Thread-level detail files: Writes one per-thread detail markdown file so you can drill into specifics without losing context.
Vault-discovered sources and contacts: Discovers the correct channels and sender-to-person attribution from your existing client and contact notes, then uses claude -p to produce summaries.
Idempotent sync with safe writes: Re-running sync overwrites the same week’s outputs and writes through obsidian eval rather than direct file edits.

Quick Start

Run comms sync for your chosen client and week so your vault receives the latest weekly rollup and thread detail files.

Frequently Asked Questions about comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate weekly client communication digests from email and Slack in Obsidian?▼

Weekly client communication digests are generated by pulling email and Slack history for a Monday to Sunday window, summarizing threads via claude, and writing idempotent markdown files to your Obsidian vault.

Can I backfill older weekly comms summaries for a specific client?▼

You can backfill older weeks by running the sync for your chosen client and target week, which pulls historical messages and overwrites the same week's outputs with idempotent markdown files.

How does the Skill discover Slack channels and email contacts for summarization?▼

Slack channels and sender-to-contact attribution are discovered by reading existing client and contact notes from your Obsidian vault frontmatter before pulling messages for the weekly window.

Do I need ProtonMail and slk to sync Slack messages and email into Obsidian?▼

Yes, protonmail-cli and slk are required dependencies to pull email and Slack message history, while obsidian eval handles writing the summarized markdown outputs into your vault.

Does running the weekly digest sync overwrite previous thread-level summary files?▼

Re-running sync overwrites the same week's outputs safely by writing through obsidian eval rather than direct file edits, ensuring idempotent weekly rollups and per-thread detail files.

What is the best way to summarize Slack threads and email history per client?▼

The best way to summarize per client is grouping messages by channel, resolving senders to vault contacts, and using claude -p to produce thread-level summaries within a weekly markdown rollup.