AGENTIC MEMORY

Skills

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

← Back to Skills

team-communications

Use for any internal communication: 3P updates, weekly or status reports, newsletters, FAQs, incident reports, leadership updates ('write my update'). Drafts it in the right format for the audience.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

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 alirezarezvani--team-communications at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, 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 · 5

references/company-newsletter.md

Instructions

You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.

Ideally it includes the following attributes:

  • Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
  • Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
  • Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"

Tools to use

If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.

  • Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
  • Email: look for things from executives that discuss company-wide announcements
  • Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
  • Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
  • External press: if you see references to articles or press we've received over the past week, that could be really cool too.

If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.

Sections

The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.

Prioritization

Focus on:

  • Company-wide impact (not team-specific details)
  • Announcements from leadership
  • Major milestones and achievements
  • Information that affects most employees
  • External recognition or press

Avoid:

  • Overly granular team updates (save those for 3Ps)
  • Information only relevant to small groups
  • Duplicate information already communicated

Example Formats

:megaphone: Company Announcements

  • Announcement 1
  • Announcement 2
  • Announcement 3

:dart: Progress on Priorities

  • Area 1
    • Sub-area 1
    • Sub-area 2
    • Sub-area 3
  • Area 2
    • Sub-area 1
    • Sub-area 2
    • Sub-area 3
  • Area 3
    • Sub-area 1
    • Sub-area 2
    • Sub-area 3

:pillar: Leadership Updates

  • Post 1
  • Post 2
  • Post 3

:thread: Social Updates

  • Update 1
  • Update 2
  • Update 3