Skill

Generate Internal Communications

Writes internal communications - 3P updates, newsletters, FAQs, status reports - by loading the matching guideline file.


70
Spark score
out of 100
Updated 29 days ago
Version 13.6.1

Add to Favorites

Why it matters

Streamline your internal communications by generating clear and concise updates, newsletters, and reports. This skill helps ensure consistent messaging across your organization.

Outcomes

What it gets done

01

Draft 3P updates (Progress, Plans, Problems)

02

Create company newsletters

03

Respond to frequently asked questions

04

Generate status and project updates

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-internal-comms-community | bash

Overview

Internal Comms Community

A skill that writes internal communications - 3P updates, newsletters, FAQs, status reports - by loading the matching per-type guideline file. Use it for recurring internal communications matching a known type; ask for clarification when the type doesn't match an existing guideline.

What it does

This skill writes internal communications by first identifying the communication type from the request, then loading the matching guideline file from an examples/ directory: 3p-updates.md for Progress/Plans/Problems team updates, company-newsletter.md for company-wide newsletters, faq-answers.md for answering frequently asked questions, or general-comms.md as a catch-all for anything that doesn't match those three. Each guideline file then specifies the formatting, tone, and content-gathering instructions to follow for that specific communication type.

When to use - and when NOT to

Use this skill to write 3P updates, company newsletters, FAQ responses, status reports, leadership updates, project updates, or incident reports. If the communication type doesn't match any existing guideline file, the skill asks for clarification or more context about the desired format rather than guessing at a structure.

Inputs and outputs

Input is the internal communication request and its type; output is a written communication following the specific format, tone, and content rules of the matching guideline file - 3P update, newsletter, FAQ answer, or general communication.

Who it's for

Teams and leaders writing recurring internal communications - progress updates, newsletters, FAQs, incident reports - who want a consistent format per communication type rather than reinventing structure each time.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.