CtrlK
BlogDocsLog inGet started
Tessl Logo

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

90

1.37x
Quality

71%

Does it follow best practices?

Impact

92%

1.37x

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is concise, well-organized, and gives a clear actionable workflow with specific file mappings, but it depends entirely on examples/ guideline files that are not present in the bundle, which undermines the progressive-disclosure design.

Suggestions

Include the referenced example guideline files (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) under examples/ so the deferred content is actually available.

Verify referenced paths against the real bundle structure and fix any mismatch between the paths named in SKILL.md and the files that exist.

Consider inlining a one-line summary of each guideline's format/tone so the skill remains useful even when a guideline file cannot be loaded.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place (a short 'when to use' list, a three-step process, and a keywords line).

5 / 5

Actionability

It gives concrete, actionable guidance with specific file paths to load per communication type ('examples/3p-updates.md', 'examples/company-newsletter.md', etc.) plus a fallback, but the actual formatting/tone instructions are deferred to files that are not bundled here.

4 / 5

Workflow Clarity

A clear three-step sequence (identify type → load guideline file → follow its instructions) with a fallback branch for unmatched types; no validation checkpoints are needed since this is a non-destructive writing task, leaving only minor gaps.

4 / 5

Progressive Disclosure

The structure is well-intended (overview pointing to one-level-deep, clearly labeled files), but every referenced guideline file under examples/ is missing from the bundle, so navigation is broken and the deferred content is unreachable.

3 / 5

Total

16

/

20

Passed

Description

65%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 clearly scopes a distinct niche and provides explicit trigger guidance with many natural terms, but its capability statement is generic ('a set of resources to help me write') and uses first-person voice, which weakens specificity.

Suggestions

Replace first-person phrasing with third person and list concrete actions, e.g. 'Drafts and formats internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports) using company-standard templates.'

Sharpen the 'what' by stating the concrete actions performed (draft, format, structure) rather than 'a set of resources to help me write'.

Add a couple of common synonyms users might say (e.g. 'weekly update', 'team update', 'all-hands update') to round out trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and lists many concrete communication types but offers only one generic action ('write ... using the formats that my company likes to use'); it is reduced from a base of 3 to 2 by the first-person phrasing 'to help me write'.

2 / 5

Completeness

Both 'what' ('a set of resources to help me write all kinds of internal communications, using the formats that my company likes to use') and 'when' ('Claude should use this skill whenever asked to write some sort of internal communications (...)') are present with concrete triggers, but the 'what' is somewhat vague ('a set of resources') rather than listing concrete actions.

4 / 5

Trigger Term Quality

It includes natural terms a user would say ('status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates') with good coverage, though a few common synonyms are missing and some terms are company-specific jargon.

4 / 5

Distinctiveness Conflict Risk

Internal communications is a clear niche with distinct triggers (3P updates, company newsletters, incident reports), with only minor overlap risk against generic writing or status-update skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
boisenoise/skills-collections
Reviewed

Table of Contents

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.