internal-comms
Write internal communications using company formats. Use when writing
Best use case
internal-comms is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Write internal communications using company formats. Use when writing
Teams using internal-comms should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/internal-comms/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How internal-comms Compares
| Feature / Agent | internal-comms | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Write internal communications using company formats. Use when writing
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ## 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.
Related Skills
conducting-internal-reconnaissance-with-bloodhound-ce
Conduct internal Active Directory reconnaissance using BloodHound Community Edition to map attack paths, identify privilege escalation chains, and discover misconfigurations in domain environments.
conducting-internal-network-penetration-test
Execute an internal network penetration test simulating an insider threat or post-breach attacker to identify lateral movement paths, privilege escalation vectors, and sensitive data exposure within the corporate network.
jepsen-testing
Jepsen-style correctness testing for distributed systems under faults (partitions, crashes, clock skew) using concurrent operation histories and formal checkers (linearizability/serializability and Elle-style anomalies). Use when designing, implementing, or running Jepsen tests, or interpreting histories/violations.
Deterministic Color Generation via Metadata Hashing
**Status**: ✅ Production Ready
cyton-dongle
Connect and stream from OpenBCI Cyton/Daisy via USB dongle, including first-time radio channel pairing
asi-transient-agenda
Org-agenda-like transient views for ASI skill orchestration via nbb/squint + Emacs hydra
Topological Superintelligence (TSI)
Compositional AI framework using GF(3) triadic balance and category-theoretic foundations.
zx-calculus
Coecke's ZX-calculus for quantum circuit reasoning via string diagrams with Z-spiders (green) and X-spiders (red)
zulip-cogen
Zulip Cogen Skill 🐸⚡
zls-integration
zls-integration skill
zig
zig skill
zig-syrup-bci
Multimodal BCI pipeline in Zig: DSI-24 EEG, fNIRS mBLL, eye tracking IVT, LSL sync, EDF read/write, GF(3) conservation