Generate a structured pre-read document for a customer meeting by gathering and synthesizing Slack threads, Jira issues, and manual context. Use this skill whenever the user mentions pre-read, meeting prep, customer briefing, account summary, customer deep-dive, QBR prep document, or wants to compile Slack + Jira history into a concise summary for a specific customer. Also trigger when the user pastes multiple Slack thread URLs and asks for a summary or synthesis.
Produce a concise, detail-rich pre-read document for a customer meeting. The pre-read synthesizes information from three sources: Slack threads, Jira issues, and manual context you provide. The output is a single Markdown file that distills potentially hundreds of messages into a structured briefing.
Customer accounts accumulate history across many Slack threads (external channels, internal channels, engineering discussions) and Jira tickets. Before a meeting, an SE needs a single document that captures the full picture: what happened, what's configured, what's broken, what's pending. Reading all the threads manually takes hours. This skill does the reading and produces the briefing.
/slack-setup done, credentials in ~/.fe-skills/.env)/atlassian-setup done, credentials in ~/.fe-skills/.env)uv sync in each skill directory)When the user invokes this skill, collect three categories of input. Not all are required — the skill works with whatever is available.
Used to:
--customer CustomerName)"CustomerName" in:#channel)Accept threads in two ways:
Pasted URLs — the user gives specific thread links: