internal-comms

Write internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, and project updates using repeatable internal formats.

Quality

61%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/internal-comms/SKILL.md

Quality

Content

57%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 skill functions primarily as a routing table to external guideline files, which is a reasonable architectural choice but leaves the SKILL.md itself with very little standalone actionable content. The workflow is simple and clear but lacks any concrete examples, templates, or inline guidance that would make it useful if the referenced files were unavailable. The conciseness is good, but the skill trades too much substance for brevity.

Suggestions

Add at least one inline example of a completed communication (e.g., a short 3P update) so the skill has standalone value even without the referenced files.

Include a brief summary of the key formatting or tone guidelines for each communication type directly in the SKILL.md, rather than deferring everything to external files.

Add a light validation step such as 'Review the draft against the guideline's tone and format checklist before presenting to the user.'

Dimension	Reasoning	Score
Conciseness	The content is fairly lean and doesn't over-explain concepts Claude already knows. The keywords section at the bottom is somewhat unnecessary padding, and the final sentence about asking for clarification is implicit behavior Claude would already exhibit, but overall it's efficient.	4 / 5
Actionability	The skill provides a clear routing mechanism to specific guideline files, but the actual actionable content is entirely deferred to those files. The SKILL.md itself contains no concrete examples, templates, or executable guidance—it's essentially a dispatcher with no inline substance.	3 / 5
Workflow Clarity	The three-step workflow (identify type → load file → follow instructions) is clear and logically sequenced, but there are no validation checkpoints or feedback loops. For a non-destructive writing task this is less critical, but there's no mention of reviewing output against guidelines or confirming with the user.	3 / 5
Progressive Disclosure	The skill references four specific guideline files in the examples/ directory, which is a good progressive disclosure pattern. However, no bundle files were provided, so we cannot verify these references exist. The references are clearly signaled and one-level deep, but the SKILL.md provides almost no standalone value without those files—it's overly dependent on external content with no inline fallback or summary of what each guideline contains.	3 / 5
	Total	13 / 20 Passed

Description

66%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 does a good job enumerating specific internal communication types, providing strong trigger terms for skill selection. Its main weakness is the absence of an explicit 'Use when...' clause, which limits completeness and makes it harder for Claude to know precisely when to select this skill over a general writing skill. Adding trigger guidance and a few more synonym terms would elevate this description significantly.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to draft or update internal communications such as status reports, team updates, or incident summaries.'

Include additional natural synonyms like 'team update,' 'weekly report,' 'stakeholder update,' 'internal memo,' or 'comms' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific document types (status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, project updates) and mentions 'repeatable internal formats.' Minor gap: doesn't describe what actions beyond 'write' (e.g., editing, formatting, templating).	4 / 5
Completeness	The 'what' is clear — writing various internal communications using repeatable formats. However, there is no explicit 'when' clause (e.g., 'Use when...'), which per the rubric guidelines should cap this dimension at 3.	3 / 5
Trigger Term Quality	Includes many natural terms users would say: 'status reports,' 'leadership updates,' 'newsletters,' 'FAQs,' 'incident reports,' 'project updates.' Missing some synonyms like 'team update,' 'weekly report,' 'stakeholder update,' 'comms,' or 'internal memo.'	4 / 5
Distinctiveness Conflict Risk	The focus on 'internal communications' with specific document types like incident reports, FAQs, and 3P updates creates a fairly distinct niche. Minor overlap risk with general writing or external communications skills, but the internal focus and enumerated types reduce conflict.	4 / 5
	Total	15 / 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: plugins/AI-Agents-Safe-Coding-Skills/skills/internal-comms/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.