CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exec-comms

Rewrite an exec update, memo, strategy doc, deck outline, Slack post or talk so it lands with senior people, and get a graded score plus the top 3 fixes. Use when you say 'rewrite this for my VP', 'exec update', 'how do I present to the CEO', 'my memo is too long', 'prep me for this review', 'all-hands talk' or 'I get nervous presenting'. Draws on 296 insights from 90 Lenny's Podcast guests incl. Wes Kao, Nancy Duarte and Matt Abrahams.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, well-structured playbook that is exceptionally actionable for a judgment-based skill: routing table, per-play steps, explicit done-tests, a grading rubric, and a fill-in deliverable template. Its main costs are token duplication (inline quotes vs references/quotes.md) and repeated principles across sections.

Suggestions

Replace the inline 'Receipts' quotes with a one-line pointer to references/quotes.md (keeping at most one anchor quote) to remove duplication and reduce body tokens.

Consolidate the point-first/ask-separation guidance that currently recurs in Play A, 'Where the experts disagree', 'Red flags', and the grade table into a single statement plus cross-references.

Move the full 'Grade existing work' 7-criterion rubric into references/frameworks.md and keep only the criterion names and total in the body, since the per-cell 1/3/5 anchors are reference material.

DimensionReasoningScore

Conciseness

Nearly every sentence carries non-obvious, guest-sourced guidance with no concept explanations, but the 'Receipts' section duplicates six quotes already in references/quotes.md, and point-first/ask-clarity principles recur across Play A, 'Where the experts disagree', 'Red flags' and the grade table, so some trimming is possible.

4 / 5

Actionability

Fully executable for an instruction-only skill: concrete tag scales ('#FYI / #suggestion / #recommendation / #plea'), a specific 60-second opener sequence, a copy-paste 'Exec Comms Pack' deliverable template, and a 7-criterion grading rubric with 1/3/5 anchors and 'Score each 1 to 5... Return scores, the total, and the top 3 fixes'.

5 / 5

Workflow Clarity

Clear three-step sequence (Diagnose with 'max 4' questions, a situation→play routing table, per-play steps) with explicit checkpoints: 'Done when a stranger can state the point and the ask in one breath', 'Read it aloud; if it sounds complicated, write what you would say', 'Expect to trim at least 20%', plus the grade rubric and red flags as feedback loops.

5 / 5

Progressive Disclosure

Good structure with well-signaled, real, one-level-deep references ('references/frameworks.md — every framework in this skill, how to run it'), but the 'Receipts' section inlines content duplicated in references/quotes.md and the body carries substantial detail that sits at the boundary of what belongs in the bundle files.

4 / 5

Total

18

/

20

Passed

Description

91%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 description: concrete capabilities, an explicit 'Use when' clause with natural trigger quotes, and a well-delineated executive-communication niche. The only deductions are the second-person 'Use when you say' phrasing and slight overlap risk from a couple of generic-sounding triggers.

Suggestions

Rewrite the trigger clause in third person, e.g. 'Use when the user says "rewrite this for my VP"...', to avoid the second-person voice penalty.

Anchor the two broadest triggers to the exec context, e.g. 'my exec memo is too long' or 'I get nervous presenting to leadership', to reduce overlap with generic writing and public-speaking skills.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with comprehensive artifact coverage ('Rewrite an exec update, memo, strategy doc, deck outline, Slack post or talk', 'get a graded score plus the top 3 fixes'), which matches the 5 anchor, but 'Use when you say...' is second-person voice, and the rubric mandates a 1-point specificity penalty for second person, bringing it to 4.

4 / 5

Completeness

Both halves are explicit: 'what' is concrete (rewrite + graded score + top 3 fixes) and 'when' is a literal 'Use when you say...' clause with seven concrete trigger phrases, exactly the anchor-5 pattern.

5 / 5

Trigger Term Quality

Comprehensive natural user phrasings across the use space: 'rewrite this for my VP', 'exec update', 'how do I present to the CEO', 'my memo is too long', 'prep me for this review', 'all-hands talk', 'I get nervous presenting' — matching the rubric's good examples' pattern of concrete quoted triggers.

5 / 5

Distinctiveness Conflict Risk

Clear exec-comms niche with distinct senior-stakeholder triggers ('for my VP', 'present to the CEO', 'exec update'), but broadly-phrased triggers like 'my memo is too long' and 'I get nervous presenting' could also match generic writing-help or public-speaking skills — minor overlap risk with closely related skills, matching the 4 anchor.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

menkesu/awesome-pm-skills

Path

skills/exec-comms/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.