home / skills / plurigrid / asi / internal-comms

internal-comms skill

/skills/internal-comms

This skill writes internal communications in company formats, ensuring clear, actionable updates that fit leadership and team audiences.

npx playbooks add skill plurigrid/asi --skill internal-comms

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.5 KB
---
name: internal-comms
description: Write internal communications using company formats. Use when writing
version: 1.0.0
---


# Internal Communications

## Document Types

### Status Report
```markdown
# [Project Name] Status Report
**Date:** [Date]
**Author:** [Name]
**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked

## Summary
[2-3 sentence overview]

## Progress This Week
- Completed: [items]
- In Progress: [items]
- Blocked: [items with owners]

## Key Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric] | [Target] | [Actual] | ⬆️/➡️/⬇️ |

## Next Week
- [Planned items]

## Risks & Mitigations
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| [Risk] | H/M/L | [Action] | [Name] |

## Asks
- [Any blockers needing escalation]
```

### Leadership Update
```markdown
# [Team] Update - [Date]

## TL;DR
[One paragraph executive summary - the only thing busy execs will read]

## Wins
- [Key accomplishment with impact]
- [Key accomplishment with impact]

## Challenges
- [Challenge]: [What we're doing about it]

## Key Decisions Needed
1. [Decision]: [Context, options, recommendation]

## Metrics Dashboard
[Include 3-5 key metrics with trends]
```

### Incident Report
```markdown
# Incident Report: [Title]

**Severity:** P0/P1/P2/P3
**Duration:** [Start] - [End]
**Impact:** [User/revenue impact]
**Status:** Resolved/Monitoring/Active

## Timeline
| Time (UTC) | Event |
|------------|-------|
| [Time] | [What happened] |

## Root Cause
[Clear explanation of what went wrong]

## Resolution
[What was done to fix it]

## Action Items
| Item | Owner | Due Date | Status |
|------|-------|----------|--------|
| [Action] | [Name] | [Date] | ⬜/✅ |

## Lessons Learned
- [What we learned]
- [What we'll do differently]
```

### All-Hands Announcement
```markdown
# [Announcement Title]

Hey team,

[Opening that sets context]

**What's happening:** [Clear, simple explanation]

**Why it matters:** [Impact and benefits]

**What you need to do:** [Specific actions if any]

**Timeline:**
- [Date]: [Milestone]
- [Date]: [Milestone]

**Questions?** [Where to ask]

[Sign-off]
```

## Writing Principles

1. **Lead with the bottom line** - Busy readers skim
2. **Be specific** - Numbers > adjectives
3. **Own problems** - "We missed" not "It was missed"
4. **Action-oriented** - Every problem has a next step
5. **Appropriate tone** - Match urgency to content



## Scientific Skill Interleaving

This skill connects to the K-Dense-AI/claude-scientific-skills ecosystem:

### Graph Theory
- **networkx** [○] via bicomodule
  - Universal graph hub

### Bibliography References

- `general`: 734 citations in bib.duckdb



## SDF Interleaving

This skill connects to **Software Design for Flexibility** (Hanson & Sussman, 2021):

### Primary Chapter: 4. Pattern Matching

**Concepts**: unification, match, segment variables, pattern

### GF(3) Balanced Triad

```
internal-comms (−) + SDF.Ch4 (+) + [balancer] (○) = 0
```

**Skill Trit**: -1 (MINUS - verification)


### Connection Pattern

Pattern matching extracts structure. This skill recognizes and transforms patterns.
## Cat# Integration

This skill maps to **Cat# = Comod(P)** as a bicomodule in the equipment structure:

```
Trit: 0 (ERGODIC)
Home: Prof
Poly Op: ⊗
Kan Role: Adj
Color: #26D826
```

### GF(3) Naturality

The skill participates in triads satisfying:
```
(-1) + (0) + (+1) ≡ 0 (mod 3)
```

This ensures compositional coherence in the Cat# equipment structure.

Overview

This skill writes clear, company‑formatted internal communications for status reports, leadership updates, incident reports, and all‑hands announcements. It enforces concise structure, the company’s writing principles, and consistent metadata so messages are scannable and actionable. Use it to save time and keep stakeholders aligned with repeatable templates.

How this skill works

You provide the context (audience, project, dates, key facts, and desired tone) and the skill fills the chosen template with prioritized content, metrics tables, timelines, risks, and asks. It enforces the company writing principles: lead with the bottom line, be specific, own problems, and include next steps. Outputs are ready to paste into internal docs, Slack, or email.

When to use it

  • Weekly or sprint status reports to stakeholders
  • Executive or leadership updates that require a TL;DR
  • Post‑mortem or incident reports after outages or incidents
  • Company or team all‑hands announcements and timelines
  • When you need a consistent, audit‑friendly record of decisions and actions

Best practices

  • Start with the single most important point so skimmers get the bottom line
  • Include owners and due dates for every open item
  • Prefer concrete metrics and trends over adjectives
  • Keep action items small, testable, and assigned
  • Match tone and urgency to the audience (execs vs. engineers)

Example use cases

  • Produce a weekly project status report with completed/in‑progress/blocked sections and an asks list
  • Draft a one‑paragraph executive TL;DR plus 3–5 key metrics for leadership review
  • Create an incident report timeline, root cause, fixes, and follow‑up action items
  • Write an all‑hands announcement with clear ‘what’, ‘why’, and ‘what you need to do’ steps
  • Convert raw meeting notes into a structured leadership update with decisions and owners

FAQ

Can the output match my company’s exact template?

Yes. Provide the template or specify which of the built‑in templates to use and include any required fields; the skill will populate them consistently.

How do I include metrics and tables?

Supply metric names, targets, actuals, and trends; the skill will format a compact table and call out noteworthy deltas.

Can it produce different tones for different audiences?

Yes. Specify the tone (e.g., executive, neutral, urgent) and the skill will adjust phrasing, length, and emphasis accordingly.