Roundup Setup
Configure Roundup audiences, sources, and writing style so Copilot CLI can generate leadership or team briefings on demand.
Overview
roundup-setup is an agent skill most often used in Grow (also Operate, Build) that creates ~/.config/roundup/config.md for Copilot CLI Roundup briefings.
Install
npx skills add https://github.com/github/awesome-copilot --skill roundup-setupWhat is this skill?
- Writes editable config at ~/.config/roundup/config.md generated by roundup-setup
- Documents natural-language triggers such as use roundup and audience or time-range phrases
- Captures role, reports-to, team members, and mission for briefing context
- Style section records format, length, tone, and characteristics from your examples
- Default config path: ~/.config/roundup/config.md
Adoption & trust: 1.1k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You repeat the same context about your role, team, and writing style every time you ask Copilot for a leadership or team briefing.
Who is it for?
Indie leads and solo founders who already use Copilot CLI and want configurable weekly or ad-hoc status briefings.
Skip if: Teams not using Copilot CLI Roundup, or builders who only need a single one-off email with no recurring briefing workflow.
When should I use this skill?
User runs roundup-setup or asks to change Roundup audiences, sources, or briefing style for Copilot CLI.
What do I get? / Deliverables
A persistent Roundup config file captures audiences, sources, and style so later use roundup commands produce on-brand briefings without re-explaining your setup.
- ~/.config/roundup/config.md with role, style, and usage instructions
- Documented natural-language roundup invocation patterns
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Recurring status and stakeholder briefings compound communication discipline after you are building and shipping, which maps to Grow lifecycle rituals. Roundup setup captures role, team, style, and audience templates for ongoing update cadence—not one-off coding tasks.
Where it fits
Define leadership vs team audiences before a weekly roundup cadence.
Tune tone and bullet structure for post-incident stakeholder updates.
Capture project grouping style so briefings mirror how you report sprint progress.
How it compares
Use for durable briefing personalization instead of pasting the same context into chat each Monday.
Common Questions / FAQ
Who is roundup-setup for?
Solo builders and small-team leads using GitHub Copilot CLI who want Roundup to know their role, audiences, and update style.
When should I use roundup-setup?
Use it in Grow to establish briefing cadence; in Operate when framing production or incident summaries for stakeholders; and in Build when summarizing multi-track implementation progress for your manager or team.
Is roundup-setup safe to install?
Review the Security Audits panel on this Prism page; the skill writes local config under ~/.config/roundup/ and may reference team names you supply—avoid putting secrets in config.md.
SKILL.md
READMESKILL.md - Roundup Setup
# Roundup Configuration *Generated by roundup-setup. You can open and edit this file anytime -- your changes will be respected.* *Location: ~/.config/roundup/config.md* --- ## How to Use Roundup Generate a briefing anytime by telling Copilot CLI: - `use roundup` -- generates a briefing covering the past week; if you have one audience it uses that, and if you have multiple audiences Roundup will ask which one - `use roundup -- leadership briefing for this week` -- specify audience and time range - `use roundup -- team update since Monday` -- any natural phrasing works - `use roundup-setup` -- re-run setup to change your audiences, sources, or style --- ## Your Role - **Title:** [Your role or title] - **Team:** [Your team, org, or department] - **Reports to:** [Who you report to -- title or name] - **Team members:** [Who reports to you, or who you work closely with] - **What your team does:** [One-sentence description of your team's mission or focus area] --- ## Your Style *How you write status updates, based on your examples.* ### Format - **Structure:** [e.g., Bullet points grouped by project area / Narrative prose / Numbered items with headers] - **Typical length:** [e.g., Half a page / 5-8 bullet points / 2-3 short paragraphs] - **Uses headers or section breaks:** [Yes/No -- and what kind] - **Uses sub-bullets or nested detail:** [Yes/No] ### Tone - **Register:** [e.g., Professional and direct / Conversational / Formal executive style] - **Characteristics:** [e.g., Action-oriented, leads with outcomes, names people involved, uses specific metrics] ### Organization - **How you group information:** [e.g., By project area / By theme / Chronologically / By priority] ### Content You Typically Include - [e.g., Key accomplishments or shipped items] - [e.g., Active risks or blockers] - [e.g., Upcoming milestones or deadlines] - [e.g., Decisions made or pending] - [e.g., Items needing input from the reader] - [e.g., People updates -- who's working on what] ### Content You Typically Skip - [e.g., Routine maintenance, minor bug fixes] - [e.g., Internal process details] - [e.g., Items the audience already knows about] ### Distinctive Patterns - [e.g., Always opens with a one-line summary] - [e.g., Uses bold for action items] - [e.g., Ends with "let me know if you have questions"] - [e.g., Separates risks into their own section at the end] --- ## Audiences *To add a new audience, copy one of the sections below and change the details.* ### [Audience Name] - **Who:** [Description of this audience -- e.g., "My VP and their chief of staff"] - **What they care about:** [Themes or priorities this audience focuses on] - **Detail level:** [Big picture only / Moderate detail / Full play-by-play] - **Format preferences:** [Any audience-specific format rules -- e.g., "three bullets max," "wants a narrative paragraph"] - **Cadence:** [How often -- weekly, biweekly, ad-hoc, before a specific meeting] - **Style differences from default:** [How this audience's version differs from your standard style, if at all] *Repeat this section for each audience.* --- ## Information Sources ### Tools Available *Data sources roundup can pull from automatically in your current setup.* - [ ] **GitHub** -- repos: [list specific repos, orgs, or "all repos I have access to"] - [ ] **M365 (WorkIQ)** -- email, Teams, calendar - [ ] **Slack** -- channels: [list channels to monitor] - [ ] **Google Workspace** -- Gmail, Calendar, Drive - [ ] **Other:** [describe any other connected sources] ### Specific Places to Look - **For work product and project activity:** [specific repos, boards, trackers, documents] - **For conversations and decisions:** [specific channels, threads, email lists, meeting series] - **For upcoming items and deadlines:** [calendars, project milestones, roadmap docs] ### Known Gaps *Sources you mentioned during setup that aren't currently connected. For these, you'll need to paste relevant context when generating a briefing.*