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

65%

Does it follow best practices?

Impact

95%

1.58x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/internal-comms/SKILL.md

The canonical home for this skill is internal-comms in anthropics/skills

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is well-organized and concise with a clear routing workflow, but it is fundamentally incomplete: every piece of substantive guidance is deferred to examples/*.md files that are not present in the bundle, so Claude cannot actually follow the workflow end-to-end.

Suggestions

Add the missing bundle files (examples/3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) so the referenced detailed guidance actually exists.

Include at least a brief, concrete summary of the formatting/tone conventions for each communication type in SKILL.md (or its files) rather than only routing to them.

Remove the redundant communication-type list — it currently appears in the description, the "When to use" section, and the "How to use" examples list.

Dimension	Reasoning	Score
Conciseness	The body is lean and doesn't explain concepts Claude already knows, but the communication-type list is repeated three times (in the description, the "When to use" section, and the examples list), so it could be tightened.	2 / 3
Actionability	It gives a concrete routing procedure with named files, but the substantive guidance ("Follow the specific instructions in that file for formatting, tone, and content gathering") is delegated to examples/*.md files that do not exist in the bundle, leaving the actual writing instructions missing.	2 / 3
Workflow Clarity	The 3-step sequence is clearly ordered with an explicit fallback for unmatched types, but there are no validation checkpoints and steps 2–3 cannot actually complete because the referenced files are absent.	2 / 3
Progressive Disclosure	The references are well-signaled and one level deep (matching a strong structure), but scored against the actual bundle: no examples/, references/, scripts/, or assets/ directory exists, so all four referenced detail files are missing and the disclosure leads nowhere.	2 / 3
	Total	8 / 12 Passed

Description

80%

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 clearly answers what and when with strong, natural trigger coverage and a distinct niche, so it lands high overall. Its single weak spot is specificity: it relies on one generic verb and uses first-person voice ("help me", "my company"), which the rubric penalizes.

Suggestions

Rewrite the description in third person (e.g., "Writes internal communications..." instead of "help me write") to avoid the first-person specificity penalty.

Replace vague phrasing ("all kinds of", "the formats that my company likes to use") with the concrete actions and format types the skill actually produces.

Dimension	Reasoning	Score
Specificity	The only action verb is the generic "write" applied to a list of communication types (no multiple distinct concrete actions like the anchor-3 "extract/fill/merge"), and it is written in first person ("help me write", "my company likes to use"), which the guidelines penalize by reducing specificity by 1.	1 / 3
Completeness	It explicitly answers both "what" ("A set of resources to help me write all kinds of internal communications") and "when" ("Claude should use this skill whenever asked to write some sort of internal communications..."), with an explicit trigger clause.	3 / 3
Trigger Term Quality	It lists many natural terms a user would actually say — "status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates" — giving good coverage including common variations.	3 / 3
Distinctiveness Conflict Risk	It carves a clear internal-communications niche with distinct triggers (3P updates, newsletters, incident reports) that are unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/internal-comms/SKILL.md
Commit: 13c9cb5

Reviewed: about 22 hours 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.