Internal comms

Skill BAKUGOS1/SkilledAgents-Toolkit/plugins/skilled-agents/skills/internal-comms

Portable open-source Codex toolkit with reusable skills, custom agents, plugins, project profiles, validation tools, and SDK examples.

Install

npx -y skills add BAKUGOS1/SkilledAgents-Toolkit --skill internal-comms

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Practical internal communication writing workflow for status reports, 3P updates, leadership updates, project updates, incident reports, FAQs, launch notes, team announcements, and executive summaries. Use when the user asks to write, polish, summarize, or package work for teammates, stakeholders, leadership, or future handoff.

SKILL.md

1.8 KB, 344 tokens by cl100k_base, as published. Nobody here has run it

Internal Comms

Overview

Use this skill to write crisp internal updates that are useful, honest, and easy to scan. It is adapted from useful patterns in Anthropic's Apache-2.0 internal-comms skill, with generic formats for future projects.

Choose The Format

3P update: Progress, Plans, Problems.
Status report: current state, completed work, next steps, blockers, risks.
Leadership update: decision needed, impact, options, recommendation, timeline.
Incident report: impact, current status, timeline, root cause if known, actions.
FAQ: question, short answer, detail, owner/source.
Launch note: what changed, who it affects, rollout, support path, known limitations.
Handoff: context, files/systems touched, verification, risks, next owner.

Writing Rules

Put the key takeaway first.
Separate confirmed facts from assumptions.
Name dates, owners, and next actions.
Avoid fake certainty, hype, and unverified status claims.
Keep paragraphs short and skimmable.
Include blockers and risks plainly.
Match the audience: tactical for team, decision-focused for leadership.

Default Templates

3P Update

Progress:
Plans:
Problems:
Ask:

Project Status

Summary:
Done:
In Progress:
Next:
Risks/Blockers:
Decisions Needed:

Incident Update

Status:
Impact:
Timeline:
Mitigation:
Root Cause:
Follow-ups:

Final Handoff

Return a ready-to-send message and mention any missing facts that should be confirmed before sending.