professional-communication
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.
Install with Tessl CLI
npx tessl i github:softaworks/agent-toolkit --skill professional-communicationOverall
score
86%
Validation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
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.
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
| Dimension | Reasoning | 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 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.