written-communication

written-communication is a skill for Claude Code, Codex from cnfeat/top-pm-skills. It costs 42 tokens per session (1,043 once invoked), scanned A, original, MIT.

A writing-support tool for making memos, emails, strategy documents, announcements, and other written communication clearer, shorter, and more persuasive.

In plain words
What is it for?
Use it to organise ideas, lead with the conclusion, improve clarity, and edit business or product communications.
Why use it?
It helps remove unnecessary context, clarify the intended outcome, and make writing understandable to people unfamiliar with the subject.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to organise ideas, lead with the conclusion, improve clarity, and edit business or product communications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cnfeat/top-pm-skills/written-communication
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cnfeat/top-pm-skills --skill written-communication
Clone the repo
git clone --depth 1 https://github.com/cnfeat/top-pm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for written-communication

README.md
[![agentmods](https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/written-communication/github.svg)](https://agentmods.dev/skills/cnfeat/top-pm-skills/written-communication)
Your own site
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/written-communication"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/written-communication/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for written-communication

Your own site · 80×15
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/written-communication"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/written-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,043 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01043
Opus 5 $0.00021 $0.00522
Sonnet 5 $0.00008 $0.00209
Haiku 4.5 $0.00004 $0.00104

Measured 9d ago against content hash 8f0c4f47255b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

written-communication scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

参考skill/lenny-skills-main (2)/lenny-skills-main/skills/written-communication/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Written Communication

Help the user communicate more effectively in writing using frameworks and insights from 38 product leaders.

How to Help

When the user asks for help with written communication:

  1. Clarify the purpose - Ask what action or outcome they want from readers
  2. Apply the pyramid principle - Guide them to lead with the conclusion, not build up to it
  3. Cut ruthlessly - Help them eliminate unnecessary context and get to the point faster
  4. Test for simplicity - Ensure someone unfamiliar with the topic could understand the core message

Core Principles

Focus on the how, not the what

Wes Kao: "Most writers spend too much time on the what and the why and not enough time on how. Most readers already agree with the general premise of what you're saying." Minimize context and justification; focus on specific steps, nuances, and examples.

Writing clarifies thinking

Julie Zhuo: "I approach my writing as letters to myself. This is the framework, this is the advice I need to give myself. It was hugely helpful for clarifying my train of thought." Use writing as a tool to organize scattered thoughts and force clarity.

Writing is clarity at scale

Kevin Yien: "Writing is clarity at scale. A key component to a PM's job is creating clarity both internally and externally." Write in the voice of the customer to demonstrate deep understanding.

Every project needs one canonical doc

Naomi Gleit: "There needs to be one canonical doc. Everyone should know exactly where it is. It links to all other docs." Create a single source of truth for every project.

Communication is the job

Boz: "Communication is the job. Leadership is exclusively done through the creation of artifacts or verbalizations that affect other humans." Take extreme ownership of whether your message was successfully received.

Start right before the bear attack

Wes Kao: "Don't start talking about going to REI to buy a Patagonia jacket. Start right before your friend left a Clif Bar out and you almost got mauled by a bear." Cut preamble and start at the point of highest tension or relevance.

Read the full file on GitHub · 84 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 84 lines · 42 tokens per session scan A 8f0c4f47255b

Subscribe to this mod's changes

written-communication is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,043 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories