internal-comms

A set of resources to help write internal communications in common company formats. Use when asked to write internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

Quality

75%

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 ./packages/builtin-skills/skills/internal-comms/SKILL.md

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

Quality

Content

67%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 admirably concise and reasonably well-sequenced, but its progressive-disclosure design is undermined by referencing an `examples/` directory with four files that are not present in the bundle, leaving the actual guidance unactionable. The workflow is clear for a single-purpose skill but relies entirely on missing references.

Suggestions

Add the referenced `examples/` directory with the four files (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) so the progressive-disclosure links resolve to real content.

Inline a brief, concrete formatting template for at least the most common type (e.g., 3P updates: Progress/Plans/Problems headers) so the skill is actionable even before loading an example file.

Either remove the broken `examples/` references or replace them with references that match files actually shipped in the bundle, so navigation is not broken.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient, with no padding or explanations of concepts Claude already knows; every line (use-cases, three-step workflow, keywords) earns its place.	5 / 5
Actionability	It gives a clear procedure (identify type, load a named file, follow its instructions) but no executable formatting/tone guidance is inlined — all concrete guidance is deferred to the example files, and those files do not exist in the bundle, so the actionable content is largely absent.	3 / 5
Workflow Clarity	The three steps are clearly sequenced and numbered, and it includes an explicit fallback ('ask for clarification') for unmatched types; however there are no validation checkpoints, though the skill is low-risk and single-purpose.	4 / 5
Progressive Disclosure	The structure is well-intended (overview pointing to four named example files), but the referenced `examples/` directory and its four files (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) do not exist in the bundle, so the references are dead links and navigation is broken.	2 / 5
	Total	14 / 20 Passed

Description

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

A strong description that clearly states both capability and trigger conditions with a concrete enumerated list of communication types. It is mostly distinct and uses third-person voice, with only minor gaps in trigger-term synonyms and action-verb specificity.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete communication formats ('status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates'), naming the domain and several specific actions, though the action verb ('help write') is somewhat generic compared to the comprehensive anchor.	4 / 5
Completeness	It explicitly answers both 'what' ('A set of resources to help write internal communications in common company formats') and 'when' ('Use when asked to write internal communications ...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It includes natural terms users would say ('status reports', 'leadership updates', 'company newsletters', 'FAQs', 'incident reports') plus an explicit 'Use when' clause, but is missing some common synonyms and shorthand variations users might naturally employ.	4 / 5
Distinctiveness Conflict Risk	The 'internal communications' niche is fairly distinct with format-specific triggers, but the broad phrase 'internal communications' has minor overlap risk with general writing or email skills.	4 / 5
	Total	17 / 20 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: shareAI-lab/Kode-CLI
Path: packages/builtin-skills/skills/internal-comms/SKILL.md
Commit: c7f6fcc

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.