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:davepoon/buildwithclaude --skill internal-comms87
Quality
83%
Does it follow best practices?
Impact
95%
1.58xAverage score across 3 eval scenarios
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 rubric guidelines, and the capabilities are described somewhat vaguely ('resources to help') rather than with concrete action verbs. The extensive list of document types provides good distinctiveness.
Suggestions
Rewrite in third person voice: change 'help me write' to 'Drafts and formats' or 'Generates'
Add more specific action verbs describing what the skill does: 'Drafts, formats, and structures internal communications following company templates'
| 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 | Good coverage of natural terms users would say: 'status reports', 'leadership updates', '3P updates', 'company newsletters', 'FAQs', 'incident reports', 'project updates', and 'internal communications' are all phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to internal communications but could overlap with general writing skills or other document-focused skills. The company-specific formatting angle helps distinguish it somewhat. | 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 organization and progressive disclosure. However, the skill's value depends entirely on the quality of the referenced files - the SKILL.md itself provides no concrete examples or formatting guidance.
Suggestions
Consider adding one brief inline example of a common communication type (e.g., a 3P update snippet) so Claude has immediate context without loading external files
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 content is lean and efficient, with no unnecessary explanations. Every line serves a purpose - listing communication types, providing file paths, and giving clear instructions. | 3 / 3 |
Actionability | Provides clear file paths and a 3-step process, but the actual guidance is delegated to external files. The skill itself doesn't contain executable examples or concrete formatting instructions - it's essentially a routing document. | 2 / 3 |
Workflow Clarity | For a routing/dispatch skill, the workflow is clear and unambiguous: identify type → load appropriate file → follow instructions. The fallback case (ask for clarification) is also specified. | 3 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure - the SKILL.md serves as a clear overview with well-signaled one-level-deep references to specific guideline files in the examples/ directory. | 3 / 3 |
Total | 11 / 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 | |
- 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.