internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (devlog reports, leadership updates, 22A updates, 22B consended, company newsletters, FAQs, incident reports, project updates, etc.).
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
When to use this skill
To write internal communications, use this skill for:
- 22A full updates (Progress, Plans, Problems)
- 22B condensed (Progress, Plans, Problems)
- devlog updates
- Status reports
- Leadership updates
- Project updates
- Incident reports
How to use this skill
To write any internal communication:
- Identify the communication type from the request
-
Load the appropriate guideline file from the
examples/directory:-
examples/form-22a.md- For Progress/Plans/Problems team updates -
examples/devlog.md- For devlogs -
examples/form-22b.md- Baby version of the 22A -
examples/general-comms.md- For anything else that doesn't explicitly match one of the above
-
- Follow the specific instructions in that file for formatting, tone, and content gathering
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
Keywords
22A updates, 22B variant, devlogs, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-03-03
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!