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

72%Weight 40%Scale 1-5

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

The content is concise and well-structured with a clear overview pointing one level deep to per-type guideline files, which is the right shape for progressive disclosure. It is let down by missing validation steps in the workflow and by example files that are referenced but not actually bundled.

Suggestions

Add the referenced example files (examples/3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) to the skill bundle so the navigation resolves.

Insert a lightweight validation checkpoint in the workflow, e.g. a step that confirms the loaded guideline matches the requested communication type before drafting.

Specify the fallback branch more concretely (what context or format details to ask for when no guideline matches) rather than a single 'ask for clarification' line.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient: section headers, a short bulleted trigger list, a numbered 3-step process, and a keyword line, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill — it names the exact example files to load per communication type — but the actual formatting/tone instructions live in the (unbundled) example files rather than inline.	4 / 5
Workflow Clarity	The three steps (identify type → load guideline file → follow its instructions) form a clear sequence, but there are no validation or verification checkpoints and the final fallback ('ask for clarification') is only weakly specified.	3 / 5
Progressive Disclosure	Structure and one-level-deep references to examples/*.md are clearly signaled and well organized, but the referenced example files do not exist in the skill bundle, so the navigation points to files that cannot be loaded.	3 / 5
	Total	15 / 20 Passed

Description

73%Weight 40%Scale 1-5

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 is strong on completeness and trigger coverage, clearly pairing a 'what' with an explicit 'when' and listing concrete communication types. Its main weaknesses are the thin, generic action verb ('write') and the first-person voice, which the rubric penalizes on specificity.

Suggestions

Rewrite in third person and replace the generic 'write' with concrete actions (e.g. 'Drafts, formats, and structures internal communications such as status reports, 3P updates, and incident reports').

Tighten the broad opening ('all kinds of internal communications') to the specific enumerated set to further reduce overlap risk.

Surface common synonyms like 'weekly update' or 'team update' in the description so the trigger term coverage matches the body's Keywords section.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete communication types (status reports, 3P updates, incident reports, etc.) but the only action verb is the generic 'write', and the first-person voice ('to help me write', 'my company likes') triggers the rubric's one-point specificity penalty.	2 / 5
Completeness	It explicitly states both what it does ('resources to help... write... internal communications') and when Claude should use it ('whenever asked to write some sort of internal communications'), with concrete enumerated trigger cases.	5 / 5
Trigger Term Quality	It includes natural user phrases such as 'status reports', 'leadership updates', 'company newsletters', 'FAQs', and 'incident reports', with only a few common synonyms (e.g. 'weekly update') absent.	4 / 5
Distinctiveness Conflict Risk	The named internal-comms formats carve out a clear niche with low overlap risk, though the opening phrase 'all kinds of internal communications' is slightly broad.	4 / 5
	Total	15 / 20 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: a9fa86d

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