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 ./.trae/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 effectively communicates when to use the skill with a clear 'Use when' equivalent and a comprehensive list of document types as trigger terms. However, it uses first person ('help me write') which violates the third-person voice requirement, and the actual capabilities are vaguely described as just 'write' without specifying concrete actions like applying templates, formatting, or structuring content.
Suggestions
Switch from first person ('help me write') to third person voice (e.g., 'Drafts and formats internal communications using company-preferred templates and styles').
Add more specific concrete actions beyond 'write' — e.g., 'Applies company formatting standards, structures content with appropriate headers and sections, generates drafts from bullet points or meeting notes'.
| 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 beyond 'write'. It lacks specifics about what the skill actually does (e.g., applies templates, formats content, follows company style). | 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 examples). | 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 the focus on internal communications with company-specific formats provides some distinctiveness, the broad scope of 'all kinds of internal communications' could overlap with general writing skills or other document-creation skills. The mention of company-specific formats helps somewhat 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 document that efficiently directs Claude to the appropriate guideline file based on communication type. Its main weakness is that it contains no inline examples or concrete guidance itself—all substance is deferred to external files, making it impossible to evaluate the actual quality of the instructions Claude will follow. A brief example of expected output format or tone for at least one communication type would strengthen actionability.
Suggestions
Add at least one brief inline example (e.g., a short 3P update sample) so Claude has immediate context even before loading the external file.
Add a verification step in the workflow, such as 'Confirm the draft matches the tone and format guidelines before presenting to the user.'
| 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 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 (identify type → load file → follow instructions) is clear and sequenced, but there's no validation or feedback loop. 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 | Excellent progressive disclosure structure. The SKILL.md serves as a concise routing overview with clearly signaled one-level-deep references to specific guideline files in the examples/ directory. Each communication type maps to a specific file. | 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.