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.).
83
77%
Does it follow best practices?
Impact
95%
1.58xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/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 good completeness with an explicit 'when to use' clause. However, it uses first person ('help me write') which violates the third-person voice requirement, and the capabilities are described more as a list of document types rather than concrete actions. The broad scope of 'all kinds of internal communications' could create overlap with more specialized skills.
Suggestions
Rewrite in third person voice (e.g., 'Drafts and formats internal communications...' instead of 'help me write'). First person usage should be avoided per the rubric guidelines.
Add more specific action verbs describing concrete capabilities beyond just 'write' — e.g., 'Drafts, formats, and structures internal communications following company-specific templates and conventions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (internal communications) and lists several document types (status reports, leadership updates, newsletters, FAQs, incident reports, etc.), but does not describe concrete actions like 'drafts', 'formats', or 'generates'. It says 'write' once but mostly enumerates types rather than specific capabilities. | 2 / 3 |
Completeness | The description answers both 'what' (write internal communications using company-preferred formats) and 'when' ('whenever asked to write some sort of internal communications') with an explicit trigger clause and enumerated examples of when to use it. | 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', and the general term 'internal communications'. These are terms users would naturally use when requesting these documents. | 3 / 3 |
Distinctiveness Conflict Risk | While 'internal communications' is a reasonably specific niche, terms like 'FAQs', 'incident reports', and 'project updates' could overlap with other skills focused on those specific document types. The scope is broad enough to potentially conflict with more specialized writing skills. | 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 is a well-organized routing skill that efficiently directs Claude to the appropriate guideline file based on communication type. Its main weakness is that it contains no concrete examples or inline guidance—all substance is deferred to referenced files that weren't provided for evaluation. The workflow is clear but lacks any verification or quality-check steps.
Suggestions
Add at least one brief inline example showing expected output format or tone for the most common communication type (e.g., a 3P update snippet) so the skill has some standalone actionability.
Add a verification step to the workflow, such as 'Confirm the draft matches the tone and format guidelines before presenting to the user' or 'Review against the checklist in the guideline file.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what internal communications are or how Claude should think about them. Every line serves a purpose—listing types, mapping to files, and providing a fallback. | 3 / 3 |
Actionability | The skill provides a clear routing mechanism to guideline files, but the actual actionable content is deferred entirely to the referenced files. The skill itself contains no concrete examples of output format, tone, or structure—it's a dispatcher rather than an instruction set. | 2 / 3 |
Workflow Clarity | The three-step workflow (identify type → load file → follow instructions) is clear and sequenced, but there are no validation checkpoints or feedback loops. For instance, there's no step to verify the output matches the expected format or to confirm with the user before finalizing. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as an overview that clearly signals one-level-deep references to specific guideline files in the examples/ directory. Each reference is clearly labeled with its purpose, making navigation straightforward. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.