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
92%
1.37xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/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 provides good trigger term coverage and completeness with an explicit 'when to use' clause and enumerated document types. 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 'write' 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 concrete actions beyond 'write' — e.g., 'Applies company templates, structures sections with standard headers, follows approved tone and formatting guidelines for internal documents.'
| 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 sections, follows tone guidelines). | 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 '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, the broad scope ('all kinds of internal communications') and generic writing focus could overlap with general writing skills or other document-creation skills. The company-specific format angle helps somewhat but isn't strongly distinctive. | 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 strength is conciseness and clear progressive disclosure structure. Its weakness is that the SKILL.md itself contains no concrete examples or actionable content—all substance is deferred to referenced files that weren't provided for evaluation, making it impossible to assess whether the skill as a whole delivers on its promise.
Suggestions
Add at least one brief inline example of expected output format (e.g., a short 3P update snippet) so the skill provides some actionable guidance even before loading referenced files.
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 think about them. Every line serves a purpose—listing types, mapping to files, and providing a clear 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.md 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. For instance, there's no step to verify the output matches the expected format or to confirm with the user before finalizing. The fallback for unmatched types is mentioned but could be more structured. | 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. However, no bundle files were provided to verify the referenced paths actually exist. | 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
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.