tessl install https://github.com/softaworks/agent-toolkit --skill professional-communicationgithub.com/softaworks/agent-toolkit
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.
Average Score
84%
Content
85%
Description
77%
Generated
Validations
Total score
13/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 268 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'professional-communication' | |
description_field 'description' field is valid (296 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' contains unusual tool name(s) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 3
Total score
11/12| Dimension | Score |
|---|---|
conciseness The skill contains useful frameworks but is verbose in places. Sections like 'When to Use This Skill' and 'Overview' explain concepts Claude already understands (what professional communication is). The keyword list and some explanatory text could be trimmed. | 2/3 |
actionability Provides concrete, copy-paste ready templates (email structure, meeting summary format), specific examples in tables (jargon translations, subject line formulas), and actionable checklists. The guidance is specific and immediately usable. | 3/3 |
workflow_clarity For an instruction-only skill about communication, the workflows are clear. Meeting communication has explicit before/during/after sequence. The What-Why-How framework provides clear structure. The checklist at the end serves as validation for any communication task. | 3/3 |
progressive_disclosure Well-organized with clear sections and appropriate references to external files (email-templates.md, meeting-structures.md, jargon-simplification.md). References are one level deep and clearly signaled. Content is appropriately split between overview and detailed reference materials. | 3/3 |
Suggestions
Remove the 'Overview' paragraph and 'When to Use This Skill' section - Claude understands when communication guidance applies
Eliminate the keyword list - this is metadata that doesn't help Claude execute the skill
Condense the 'Core principle' and explanatory text throughout; lead directly with frameworks and examples
Overall Assessment
This is a well-structured communication skill with strong actionability through concrete templates, examples, and checklists. The progressive disclosure is excellent with clear navigation to reference materials. The main weakness is verbosity - the skill explains concepts Claude already knows and could be tightened by 20-30% without losing value.
Description
Suggestions 2
Total score
10/12| Dimension | Score |
|---|---|
specificity Lists multiple specific concrete actions: 'email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences' - these are distinct, actionable capabilities. | 3/3 |
completeness Clearly answers both what (guide technical communication covering email, messaging, meetings, audience adaptation) AND when ('Use when drafting professional messages, preparing meeting communications, or improving written communication'). | 3/3 |
trigger_term_quality Includes some natural keywords like 'email', 'meeting agendas', 'professional messages', but misses common variations users might say like 'Slack message', 'write an email', 'communication tips', 'how to phrase', or 'tone'. | 2/3 |
distinctiveness_conflict_risk While it specifies 'technical communication for software developers', terms like 'professional messages' and 'written communication' are broad enough to potentially overlap with general writing or communication skills. | 2/3 |
Suggestions
Add more natural trigger terms users might say, such as 'Slack message', 'write an email to my team', 'explain to non-technical stakeholders', or 'code review feedback'
Strengthen distinctiveness by emphasizing the developer/engineering context more explicitly in the trigger clause, e.g., 'Use when developers need to communicate about code, technical decisions, or engineering topics'
Overall Assessment
This is a solid skill description that clearly articulates what it does and when to use it. The main strengths are its explicit 'Use when...' clause and specific capability listing. However, it could benefit from more natural trigger terms users would actually type and slightly more distinctive language to avoid overlap with general writing skills.