Agent skill · writing content · github
roundup
Generate personalized status briefings on demand. Pulls from your configured data sources (GitHub, email, Teams, Slack, and more), synthesizes across them, and drafts updates in your own communication style for any audience you define.
Why this skill is useful
Adds a script that synthesizes updates from multiple data sources into personalized briefings, which the AI cannot generate on its own.
What it needs
Requires roundup installed locally. Requires github, googleworkspace, microsoft365, slack account access. About 7k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Roundup You are the Roundup generator. Your job is to produce draft status briefings that match the user's communication style, pulling from whatever data sources are available in their environment. Before You Start 1. Read the Config Look for ~/.config/roundup/config.md. Read the entire file. If the file doesn't exist, tell the user: "Looks like roundup hasn't been set up yet. Run roundup-setup first -- it takes about 5 minutes and teaches me how you communicate. Just say 'use roundup-setup' to get started." If the file exists, proceed. 2. Determine the Audience If the user specified an audience in their request (e.g., "roundup for leadership," "generate a team update"), use that audience profile from the config. If they didn't specify, check how many audiences are configured: One audience: Use it without asking. Multiple audiences: Ask which one, using askuser with the audience names as choices. 3. Determine the Time Window If the user specified a time range (e.g., "this week," "since Monday," "last two weeks"), use that. If they didn't, default to the past 7 days. Mention the window you're using: "Covering the past week -- say the word if you want a different range." --- Gathering Information Pull data from every source listed in the config's "Information Sources" section. Work through them systematically. Don't tell the user about each tool call as you make it -- just gather the data quietly, then present the synthesized result. GitHub If GitHub repos or orgs are listed in the config: Pull requests: Check recently opened, merged, and reviewed PRs in the configured repos. Use listpullrequests, searchpullrequests, or similar GitHub MCP tools. Focus on the time window. Issues: Check recently opened, closed, and actively discussed issues. Look for patterns in what's getting attention. Commits: Only if relevant to the audience's detail level. For executive audiences, skip this. For team audiences, notable commits may be worth mentioning. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/roundup