CtrlK
BlogDocsLog inGet started
Tessl Logo

effective-comms

Run a prepare → review → revise pass over an agent-written user-facing output (report, status update, strategy doc, review finding, handoff, recommendation) before it is finalized. Builds a short communications brief, reviews the draft against it and against named agent-writing failure modes (assumed context, numbered references without meaning, retained rejected ideas, leaked process history, buried recommendation), then revises or flags residual risk.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable instruction skill with a clearly sequenced workflow, explicit validation checkpoints and feedback loops, and well-organized self-contained sections. It earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains basic concepts (what a report/handoff is) and every section (brief fields, C1–C7 table, fail conditions, output contract) is load-bearing procedural guidance with no padding.

3 / 3

Actionability

Gives concrete, copy-paste-ready instruction: explicit six-cell knowledge model, a C1–C7 checklist table with a 'Catches' column, enumerated Phase 3 fail conditions, and a precise output contract — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Clear prepare → review → revise sequence with explicit validation checkpoints (mark each check pass/revised/residual-risk) and feedback loops (Phase 2 → revise → re-check; Phase 3 loop until pass), matching the score-3 anchor for sequenced workflows with validation and error-recovery loops.

3 / 3

Progressive Disclosure

No bundle files are present, so the skill is self-contained; it is well-organized into clearly signaled sections (Phase 1/2/3, Stop/output contract, Boundaries & friction) with no nested references, which satisfies progressive disclosure for a reference-free skill.

3 / 3

Total

12

/

12

Passed

Description

82%

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 is specific and distinctive with good natural-term coverage, but its 'when' guidance is implicit rather than an explicit 'Use when...' trigger clause, which caps completeness. Moving the explicit trigger phrases from when_to_use into the description would lift completeness.

Suggestions

Add an explicit 'Use when ...' clause to the description listing concrete triggers (e.g. 'Use before finalizing a report, handoff, or recommendation; trigger phrases include "comms-check this", "did I bury the recommendation?"').

Pull one or two natural trigger phrases from the when_to_use field into the description so the when-guidance lives inside description itself.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Run a prepare → review → revise pass', 'Builds a short communications brief', 'reviews the draft against it and against named agent-writing failure modes ... then revises or flags residual risk', matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers 'what' (prepare→review→revise pass with named failure modes) but the 'when' is only a soft condition ('before it is finalized') with no explicit 'Use when...' trigger guidance inside the description; per the judging guideline this caps completeness at 2.

2 / 3

Trigger Term Quality

Covers natural domain terms users would say — 'report, status update, strategy doc, review finding, handoff, recommendation' — giving good, varied coverage of likely user phrasings rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — agent-written comms review against named failure modes such as 'buried recommendation' and 'leaked process history' — with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tollens-ai/effective-comms-skills
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.