Internal comms

Skill Anoxxx/skillcache/examples/internal-comms

MRU attention protocol for skills that learn from every use — zero compute

Install

npx -y skills add Anoxxx/skillcache --skill internal-comms

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
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

Write internal communications — status reports, team updates, newsletters, meeting summaries, and FAQs. Use when asked to draft a status update, write a weekly report, summarize a meeting, create a team newsletter, or write an internal FAQ. NOT for external/public communications, press releases, or customer-facing content.

The file declares its own license as Original by Anthropic (Apache 2.0). Adapted here as an adaptive skills example.. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

Internal Communications

Write clear, actionable internal communications for teams and leadership.

Document Types

Status Report

Structure: What shipped → What's blocked → What's next Length: 300-500 words Audience: Manager or skip-level leadership

Team Newsletter

Structure: Highlights → Shoutouts → Upcoming → Fun/Culture Length: 500-800 words Audience: Full team or department

Meeting Summary

Structure: Decisions made → Action items (with owners + deadlines) → Open questions Length: 200-400 words Audience: Meeting attendees + stakeholders

FAQ

Structure: Question → Concise answer → Link to more info Length: Variable (aim for 2-3 sentence answers) Audience: Varies (identify in prompt)

Writing Principles

Lead with the takeaway. Every section starts with the conclusion, then expands.
Be specific. "Shipped the auth migration" > "Made progress on the project."
Name names. Credit contributors. Include owners for action items.
Keep it scannable. Bullet points > paragraphs. Headers for each section.
Include dates. "Ships March 15" > "Ships soon."
Flag risks early. Don't bury blockers in the middle of a paragraph.

Tone

Professional but not stiff. Write like you're talking to a smart colleague, not drafting a legal document. Contractions are fine. Jargon is fine if the audience shares it — but define terms when the audience is cross-functional.

Anti-Patterns

❌ Opening with "I hope this email finds you well" or similar filler
❌ Burying the lead under context paragraphs
❌ Passive voice for accountability ("The bug was fixed" → "Alex fixed the bug")
❌ Reports longer than one page (if it's longer, it won't be read)

Adaptive Heuristics

This skill maintains a HEURISTICS.md alongside this file. Load it at skill activation. After completing the task:

Did anything unexpected happen? (failure, workaround, surprise, user correction) → Append a one-line lesson to the TOP of HEURISTICS.md.
Did you rely on an existing heuristic? → Move it to the TOP (MRU promotion).
Does a heuristic contradict this SKILL.md? → SKILL.md wins. Note the conflict in the heuristic entry.

Keep heuristics ≤ 20 entries. When full, the bottom entry is the eviction candidate.