AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

roundup-setup

Interactive onboarding that learns your communication style, audiences, and data sources to configure personalized status briefings. Paste in examples of updates you already write, answer a few questions, and roundup calibrates itself to your workflow.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--roundup-setup at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

references/config-template.md

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.

  • [e.g., Jira board -- not connected, paste ticket updates manually]
  • [e.g., Private Slack channel -- not accessible, include key messages manually]

Preferences

Always Include

  • [Standing sections or themes that should appear in every briefing]
  • [Recurring metrics or KPIs to track]
  • [Required sections your org expects]

Never Include

  • [Repos, channels, or activity types to filter out]
  • [Types of noise that aren't worth mentioning]

Other Rules

  • [Maximum length constraints]
  • [Required formatting rules]
  • [Anything else]

Your Examples

Your original examples are preserved here for reference. Roundup uses these to stay calibrated to your voice.

Example 1

[paste of first example]

Example 2

[paste of second example, if provided]

Example 3

[paste of third example, if provided]