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.).
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill internal-comms92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 93%
↑ 1.38xAgent success when using this skill
Validation for skill structure
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.
This description has strong trigger term coverage and completeness with explicit 'when to use' guidance. However, it uses first-person voice ('help me write') which violates the third-person requirement, and the capabilities are described somewhat vaguely ('resources to help') rather than with concrete action verbs. The description would benefit from more specific action language and third-person voice.
Suggestions
Rewrite in third-person voice: 'Drafts internal communications using company-preferred formats' instead of 'A set of resources to help me write'
Add concrete action verbs describing what the skill does: 'Drafts, formats, and structures internal communications' rather than 'resources to help'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists several document types (status reports, leadership updates, newsletters, FAQs, incident reports, project updates) but uses vague language like 'all kinds of internal communications' and 'resources to help' rather than concrete actions like 'drafts', 'formats', or 'generates'. | 2 / 3 |
Completeness | Clearly answers both what ('write all kinds of internal communications, using the formats that my company likes') and when ('whenever asked to write some sort of internal communications') with explicit trigger guidance and examples. | 3 / 3 |
Trigger Term Quality | Includes 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 it specifies 'internal communications' which provides some distinction, it could overlap with general writing skills or other document-focused skills. The company-specific formatting aspect helps but isn't strongly emphasized as a differentiator. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%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-structured routing skill that efficiently directs Claude to appropriate guideline files based on communication type. Its strength is in clear organization and concise presentation. The main limitation is that actionability depends entirely on the quality of the referenced files, making this skill a dispatcher rather than a self-contained guide.
Suggestions
Consider adding a brief inline example of one communication type to demonstrate expected output quality without requiring file access
Add a note about what information to gather from the user before loading guideline files (e.g., audience, urgency, key points to cover)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the necessary routing information without explaining what internal communications are or how to write them. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides clear routing to specific files but the actual actionable content is delegated to external files. The skill itself is a dispatcher rather than containing executable guidance directly. | 2 / 3 |
Workflow Clarity | For a routing/dispatcher skill, the 3-step workflow is clear and unambiguous: identify type, load appropriate file, follow instructions. The fallback behavior for unmatched types is also specified. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to specific guideline files. The organization makes it easy to navigate to the right resource. | 3 / 3 |
Total | 11 / 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.
- 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.