Name: team-communications
Rating: 71.2 (1 reviews)
Author: alirezarezvani

team-communications

Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.

Quality

87%

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

The canonical home for this skill is team-communications in alirezarezvani/claude-skills

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.

A concise, well-structured instruction skill with concrete actionable guidance and a clear workflow that includes a revision loop. The main weakness is progressive disclosure: the body routes to four reference files that are not present in the bundle, making the navigation non-functional.

Suggestions

Include the four referenced files (references/3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) in the bundle so the routing table points to real content.

Add an explicit validation checkpoint to the workflow (e.g., 'verify every metric is sourced from provided data or MCP tools before presenting the draft') to strengthen the feedback loop.

Move the per-type format, tone, and length constraints into the reference files and keep SKILL.md as a pure routing overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean overview: a routing table, a 5-step workflow, tight tone bullets, and an anti-patterns table — every section earns its place with no padding and no explanation of concepts Claude already knows, matching the 5 anchor.	5 / 5
Actionability	Concrete guidance — 'Use available MCP tools (Slack, Gmail, Google Drive, Calendar)', 'Confirm: team name (for 3Ps), time period, audience', and specific trigger→file routing — but detailed format guidance is deferred to reference files ('Follow its formatting exactly') that are not present in the bundle, leaving a minor gap at anchor 4.	4 / 5
Workflow Clarity	Clear 5-step sequence (read reference → gather inputs → clarify scope → draft → present-and-ask) with a revision loop at step 5 and an ambiguity checkpoint ('If the type is ambiguous, ask one clarifying question'); not 5 because there is no explicit validation/checklist beyond the present-and-revise loop.	4 / 5
Progressive Disclosure	Well-designed overview with one-level-deep references signaled in the routing table ('references/3p-updates.md', 'references/company-newsletter.md', 'references/faq-answers.md', 'references/general-comms.md'), but the references/ directory is absent from the bundle — the disclosure chain leads to non-existent files and is not functional, fitting anchor 3.	3 / 5
	Total	16 / 20 Passed

Description

96%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, well-structured description that explicitly covers what and when with comprehensive natural trigger terms and a clearly scoped internal-comms niche. Minor overlap risk with PM/status-reporting skills keeps distinctiveness at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists '3P updates, company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms' plus 'draft, edit, or format' — comprehensive concrete coverage of deliverable types and actions matching the 5 anchor.	5 / 5
Completeness	Explicit 'what' ('Write internal company communications' + enumerated types) and explicit 'when' ('Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like...') with concrete trigger phrases — textbook 5.	5 / 5
Trigger Term Quality	Enumerates natural terms users would say — '3P', 'weekly update', 'newsletter', 'FAQ', 'internal comms', 'status report', 'company update', 'team update', 'incident report' plus casual 'write my update' / 'summarize what my team did this week' — comprehensive coverage with synonyms.	5 / 5
Distinctiveness Conflict Risk	Clear 'internal company communications' niche with distinct triggers, but acknowledged overlap with project-management status reporting ('status reports feed into PM reporting'); mostly distinct with minor overlap risk, so anchor 4 rather than 5.	4 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/team-communications/SKILL.md
Commit: 19392f7

Reviewed: ~16 hours 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.