internal-comms-anthropic

To write internal communications, use this skill for:

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/internal-comms-anthropic/SKILL.md

Quality

Content

75%Scale 1-5

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 strength is conciseness and clear organization. Its main weakness is that all actionable content is deferred to external files that aren't provided, making the skill itself a dispatcher with no standalone value if those files are missing.

Suggestions

Provide the bundle files (e.g., examples/3p-updates.md, examples/company-newsletter.md) so the skill has actual actionable content to work with, or inline at least a brief example of one communication type.

Add a brief general tone/style guideline inline (e.g., 'Use a professional but approachable tone, keep paragraphs short') so Claude has baseline guidance even if a referenced file is missing.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Every line serves a purpose—listing communication types, mapping them to files, and providing a clear fallback. No unnecessary explanations of what internal communications are or how markdown works.	5 / 5
Actionability	The skill provides a clear routing mechanism (identify type → load file → follow instructions), but the actual actionable content is entirely deferred to the referenced example files. Without those files, Claude has no concrete guidance on formatting, tone, or structure for any communication type.	3 / 5
Workflow Clarity	The three-step workflow is clearly sequenced and easy to follow. There's a reasonable fallback for unmatched types. However, there are no validation or review checkpoints—e.g., confirming the draft meets the guideline's requirements before finalizing—though this is a non-destructive writing task so the impact is minor.	4 / 5
Progressive Disclosure	The skill appropriately delegates detailed instructions to separate files in `examples/`, with clear one-level-deep references and a well-organized routing table. However, no bundle files were provided, so we cannot verify the referenced files exist or are well-structured, which prevents a score of 5.	4 / 5
	Total	16 / 20 Passed

Description

20%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.

This description is severely incomplete—it appears to be a truncated fragment ending with a colon, suggesting the actual content was never filled in. It lacks concrete actions, trigger terms, and any 'when to use' guidance, making it nearly useless for skill selection among multiple options.

Suggestions

Complete the description with specific actions such as 'Drafts company-wide announcements, team updates, memos, and internal emails' to improve specificity.

Add an explicit 'Use when...' clause with natural trigger terms like 'memo', 'announcement', 'internal email', 'team update', 'company newsletter', or 'all-hands'.

Differentiate from general writing skills by specifying the types of internal communications and any particular tone, format, or organizational conventions this skill handles.

Dimension	Reasoning	Score
Specificity	The description names a vague domain ('internal communications') but provides no concrete actions whatsoever—no mention of what it actually does (drafts emails, writes memos, creates announcements, etc.).	1 / 5
Completeness	The description has a weak implied 'what' (writing internal communications) and no 'when' clause. The trailing 'use this skill for:' is incomplete and provides no trigger guidance, capping this score low.	2 / 5
Trigger Term Quality	The phrase 'internal communications' is a relevant keyword, but it's the only one. Missing natural terms users would say like 'memo', 'announcement', 'company email', 'all-hands update', 'newsletter', etc.	2 / 5
Distinctiveness Conflict Risk	Very broad—'internal communications' could overlap with general writing skills, email skills, or any communication-related skill. There's nothing to distinguish it from other writing or messaging tools.	2 / 5
	Total	7 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/internal-comms-anthropic/SKILL.md
Commit: fbdfd63

Reviewed: 3 days 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.