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.37x

Quality

—

Does it follow best practices?

Impact

92%

1.37x

Average score across 10 eval scenarios

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is a lean, well-structured router with concrete file references and a clear workflow-plus-fallback. Its main weakness is that the referenced example guideline files do not exist in the bundle, breaking the progressive-disclosure promise.

Suggestions

Provide the referenced `examples/` guideline files (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) so the progressive-disclosure pointers actually resolve.

Inline at least a minimal formatting template per communication type so the skill remains usable when an example file is unavailable.

Reduce redundancy between the "When to use this skill" list and the "Keywords" section, where terms like 3P updates, company newsletter, and FAQ appear in both.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows; the 3-step "How to use" process is tight and every section earns its place.	3 / 3
Actionability	Concrete routing maps each type to a specific file path (`examples/3p-updates.md`, `examples/company-newsletter.md`, `examples/faq-answers.md`, `examples/general-comms.md`), giving actionable guidance for this instruction-only skill.	3 / 3
Workflow Clarity	A clear 3-step sequence (identify type → load file → follow instructions) is paired with an explicit fallback ("If the communication type doesn't match any existing guideline, ask for clarification").	3 / 3
Progressive Disclosure	The overview uses well-signaled one-level-deep references to `examples/*.md`, but those guideline files are not present in the bundle, so the disclosure structure cannot be verified and is non-functional.	2 / 3
	Total	11 / 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 answers both 'what' and 'when' with strong natural trigger terms and a clear niche, but loses specificity from first-person voice and vague fluff. Rewriting in third person and replacing filler with concrete formats would lift it.

Suggestions

Rewrite in third person (e.g., "Helps write internal communications...") instead of first person ("help me write", "my company") to avoid the voice penalty and improve specificity.

Replace vague fluff ("all kinds of", "formats that my company likes to use") with concrete actions or specific named formats.

Dimension	Reasoning	Score
Specificity	It names the domain and lists communication types but rests on the single vague action "write" padded with fluff ("all kinds of", "formats that my company likes to use"); first-person voice ("help me write", "my company") triggers the rubric's -1 specificity penalty, dropping a base 2 to 1.	1 / 3
Completeness	It explicitly answers 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 explicit triggers.	3 / 3
Trigger Term Quality	It lists natural terms a user would actually say — "status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates" — giving good coverage of the domain.	3 / 3
Distinctiveness Conflict Risk	The internal-comms niche with specific triggers like "3P updates, company newsletters, incident reports" is clearly distinct and unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 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.