Internal Comms Skill Security Audit

2122Try to gather as much context as you can, focusing on the things that covered the time period you're writing for:23- Progress: anything between a week ago and today24- Plans: anything from today to the next week25- Problems: anything between a week ago and today262728If you don't have access, you can ask the user for things they want to cover. They might also include these things to you directly, in which case you're mostly just formatting for this particular format.29

1112- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread13- Email: look for things from executives that discuss company-wide announcements14- 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.15- 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.16- External press: if you see references to articles or press we've received over the past week, that could be really cool too.

1## Instructions2You 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.3

1112- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread13- Email: look for things from executives that discuss company-wide announcements14- 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.15- 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.16- External press: if you see references to articles or press we've received over the past week, that could be really cool too.

11You should use the company's available tools, where communication and work happens. For most companies, it looks something like this:12- Slack: questions being asked across the company - it could be questions in response to posts with lots of responses, questions being asked with lots of reactions or thumbs up to show support, or anything else to show that a large number of employees want to ask the same things13- Email: emails with FAQs written directly in them can be a good source as well14- Documents: docs in places like Google Drive, linked on calendar events, etc. can also be a good source of FAQs, either directly added or inferred based on the contents of the doc15

2425## Answer Guidelines26- Base answers on official company communications when possible27- If information is uncertain, indicate that clearly28- Link to authoritative sources (docs, announcements, emails)29- Keep tone professional but approachable30- Flag if a question requires executive input or official response

1## Instructions2You 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.34Ideally it includes the following attributes:5- 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.6- Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences

89## Tools to use10If 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.1112- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread13- Email: look for things from executives that discuss company-wide announcements14- 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.15- 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.16- External press: if you see references to articles or press we've received over the past week, that could be really cool too.17

10## Tools Available11You should use the company's available tools, where communication and work happens. For most companies, it looks something like this:12- Slack: questions being asked across the company - it could be questions in response to posts with lots of responses, questions being asked with lots of reactions or thumbs up to show support, or anything else to show that a large number of employees want to ask the same things13- Email: emails with FAQs written directly in them can be a good source as well14- Documents: docs in places like Google Drive, linked on calendar events, etc. can also be a good source of FAQs, either directly added or inferred based on the contents of the doc15