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 (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
91
77%
Does it follow best practices?
Impact
93%
1.38xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/anthropic-internal-comms/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has strong trigger term coverage and completeness, explicitly listing when to use the skill and providing many natural keywords. However, it uses first person ('help me write') which violates the third-person voice requirement, and the specificity of what the skill actually does beyond 'writing' is limited. The description would benefit from more concrete action verbs and third-person framing.
Suggestions
Rewrite in third person voice (e.g., 'Drafts internal communications using company-preferred formats' instead of 'help me write'). First person ('me') should be avoided per style guidelines.
Add more specific actions beyond 'write' — e.g., 'Drafts, formats, and structures internal communications following company templates and conventions' to increase specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (internal communications) and lists several document types (status reports, leadership updates, newsletters, FAQs, incident reports, project updates), but does not describe concrete actions beyond 'write'. It doesn't specify what the skill actually does with these formats (e.g., applies templates, follows specific structures). | 2 / 3 |
Completeness | The description answers both 'what' (write internal communications using company-preferred formats) and 'when' (explicitly states 'Claude should use this skill whenever asked to write some sort of internal communications' followed by a parenthetical list of trigger scenarios). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'status reports', 'leadership updates', '3P updates', 'company newsletters', 'FAQs', 'incident reports', 'project updates', 'internal communications'. These are terms users would naturally use when requesting these documents. | 3 / 3 |
Distinctiveness Conflict Risk | While the focus on internal communications with company-specific formats provides some distinctiveness, the broad scope ('all kinds of internal communications') could overlap with general writing skills or other document-creation skills. The mention of company-specific formats helps but isn't strongly differentiating. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured as a routing/dispatch document that efficiently directs Claude to the appropriate guideline file based on communication type. Its main strength is conciseness and progressive disclosure. Its weakness is that the skill itself contains no concrete examples, templates, or sample outputs, making it entirely dependent on the referenced files for actionability—if those files are weak, the skill provides no fallback guidance.
Suggestions
Add at least one brief inline example of a completed communication (e.g., a short 3P update) so Claude has a concrete reference even before loading the guideline file.
Add a verification step in the workflow, such as 'Confirm the identified communication type with the user if ambiguous' or 'Review output against the guideline's format checklist before presenting.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what internal communications are or how Claude should approach writing. Every line serves a purpose—routing to the right file. | 3 / 3 |
Actionability | The skill provides a clear routing mechanism to specific guideline files, but the actual actionable content (formatting, tone, examples) is entirely deferred to external files. The skill itself contains no concrete examples, templates, or executable guidance for any communication type. | 2 / 3 |
Workflow Clarity | The 3-step workflow is clear and sequenced, but there's no validation or feedback loop. For instance, there's no step to verify the output matches the guideline's format, or to confirm with the user that the right communication type was identified. The fallback instruction for unmatched types is helpful but minimal. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a concise routing overview with clearly signaled one-level-deep references to four specific guideline files in the examples/ directory. Navigation is straightforward and well-organized. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- boisenoise/skills-collections
- Commit
636b862
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.