CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

communication

Load before writing a message to a person: a reply, report, briefing, decision request, or work-item description or comment.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured instruction-only skill: the body stays a lean router with precise reading semantics and verified one-level-deep references. The only deductions are minor — kendex boilerplate padding and full delegation of writing substance to the reference files.

DimensionReasoningScore

Conciseness

The body is lean — a routing table, a precise revision-caching rule, and copy-paste install snippets with no explanation of concepts Claude already knows. The kendex 'project-instructions' boilerplate block ('Problems with a kendex-owned skill go through `kendex report`') is unrelated to the writing task and could be trimmed, matching the 'minor instances' anchor.

4 / 5

Actionability

Concrete guidance throughout: a task-to-file routing table ('Request a decision or action | questions'), exact re-read conditions, and two copy-paste-ready instruction snippets. It falls short of 5 because the actual writing rules are fully delegated to the references ('then apply them to every message') rather than given any inline substance.

4 / 5

Workflow Clarity

The sequence is unambiguous: read SKILL.md and messages once per revision, apply to every message, add only the task-needed reference, and re-read only on change or context loss, with 'revision' precisely defined. This is a simple non-destructive skill under 50 lines where the single process is fully unambiguous, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview; all four referenced bundle files (messages.md, questions.md, reports.md, voice.md) exist and are linked from a clearly-labeled task table stating exactly when to load each. References are one level deep with sibling cross-links only — no nested-reference chains — matching the well-signaled navigation anchor.

5 / 5

Total

18

/

20

Passed

Description

75%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 terse, trigger-oriented description with explicit when-guidance and distinct scope. Its main weakness is that it describes when to load the skill but not what the skill provides, leaving the capability statement implicit.

Suggestions

State what the skill provides, e.g., 'Applies writing and presentation rules for messages to a person...' so the 'what' is substantive rather than only the procedural 'Load'.

Add common trigger synonyms such as 'update', 'summary', or 'answer' alongside the existing message-type list to broaden natural keyword coverage.

Keep the enumerated message types but consider one phrase naming the skill's mechanism (reader modes, question/reply structure) to sharpen distinctiveness against generic communication skills.

DimensionReasoningScore

Specificity

It enumerates six concrete message types ('a reply, report, briefing, decision request, or work-item description or comment'), giving several specific items. It is not 5 because the only action stated is 'Load' — what the skill actually does for those messages is never described.

4 / 5

Completeness

The 'when' is explicit and concrete ('before writing a message to a person: a reply, report...'), so the missing-trigger cap at 3 does not apply. It is not 5 because the 'what' is only procedural ('Load') — the skill's actual substance of writing/presentation rules is never stated.

4 / 5

Trigger Term Quality

'reply', 'report', 'briefing', 'decision request', 'comment', and 'message to a person' are natural phrases a user would say when needing this skill. A few common variations are missing (e.g., 'update', 'summary', 'answer'), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to person-directed messages and, per the body, explicitly distinct from agent-to-agent messages, tool prompts, and documentation. Only minor overlap risk with closely related writing/communication skills, matching the 'mostly distinct' anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/communication/SKILL.md

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.