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.).

1.58x

Quality

73%

Does it follow best practices?

Impact

95%

1.58x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/internal-comms/SKILL.md

Quality

Content

64%

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 the appropriate guideline file based on communication type. Its main weakness is that it contains almost no standalone actionable content—it's entirely dependent on external files that weren't provided in the bundle. The workflow is clear but lacks validation steps to ensure output quality.

Suggestions

Include at least one inline example of a completed communication (e.g., a short 3P update) so the skill has standalone value even if referenced files are unavailable.

Add a validation step to the workflow, such as 'Review the draft against the guideline's formatting requirements before presenting to the user.'

Provide the bundle files (examples/3p-updates.md, etc.) so the progressive disclosure structure can be fully realized and verified.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what internal communications are or how Claude should write in general. Every line serves a purpose: listing communication types, mapping them 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 (formatting, tone, content gathering) is entirely deferred to the referenced files. The skill itself doesn't contain any concrete examples, templates, or executable guidance—it's essentially a dispatcher.	2 / 3
Workflow Clarity	The three-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. The fallback instruction to ask for clarification is helpful but minimal.	2 / 3
Progressive Disclosure	The skill references four specific files in the examples/ directory with clear descriptions, which is good progressive disclosure structure. However, no bundle files were provided, so we cannot verify these references actually exist. The references are one-level deep and well-signaled, but the skill is almost entirely dependent on those external files with very little standalone value.	2 / 3
	Total	9 / 12 Passed

Description

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 lists many trigger terms and explicitly addresses both what the skill does and when to use it, which are its main strengths. However, it uses first person ('help me write') which is a voice violation, the actual capabilities are vaguely described as just 'write' without specifying concrete actions like templating or formatting, and the scope is broad enough to potentially conflict with other writing skills.

Suggestions

Replace first person 'help me write' with third person voice, e.g., 'Generates internal communications using company-approved formats and templates'.

Add more specific concrete actions beyond 'write', such as 'applies standard templates, structures sections per company guidelines, maintains appropriate tone for audience level'.

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' (explicitly states 'Claude should use this skill whenever asked to write some sort of internal communications' followed by a parenthetical list of trigger scenarios).	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, 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

Validation

90%

Warnings & errors only

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: 8c53c59

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.